Update memories MCP tool

• MCP tool name: Update_Memories
• Data type: Memory data type
• Returns: Memory MCP response
• Annotations: Not read only, not destructive, idempotent, closed world
• Surfaces: GovTribe AI (when memories are enabled)

Examples

Update the canonical memory instead of creating a duplicate when the user changes a durable preference. Use lifecycle arguments for memories that should remain reviewable by GovTribe AI. Legacy or permanent memories that do not already have a future review date must include a future expires_at before they can be updated.

At least one update action is required: memory, expires_at, strength, or reinforce. To reinforce or weaken an existing lifecycle-managed memory without changing the text, pass reinforce or strength and leave memory out.

Update an existing memory about saved-search cadence

{
  "tool": "Search_Memories",
  "arguments": {
    "query": "saved search notification cadence",
    "search_mode": "keyword",
    "size": 5
  }
}

{
  "tool": "Update_Memories",
  "arguments": {
    "memory_id": "<memory_govtribe_id>",
    "memory": "The user prefers weekly saved-search notification examples by default, but uses instant notifications for time-sensitive recompetes."
  }
}

Reinforce a lifecycle-managed memory

{
  "tool": "Update_Memories",
  "arguments": {
    "memory_id": "<memory_govtribe_id>",
    "reinforce": true,
    "reason": "The same preference was useful in another saved-search workflow."
  }
}

Weaken a lifecycle-managed memory and set a new review date

{
  "tool": "Update_Memories",
  "arguments": {
    "memory_id": "<memory_govtribe_id>",
    "expires_at": "2026-10-15",
    "strength": "weak",
    "reason": "The preference may only apply during the current capture planning period."
  }
}

Related articles

• Memory MCP response: Review the response shape returned by this tool.
• Memory data type: Understand the shared record fields and relationships used by this tool.
• GovTribe AI: Review the GovTribe AI surface where this tool can be called.
• Source identifiers and record matching: Use GovTribe IDs and source identifiers when passing records between tools.