Convocore

update_conversation_messages

Destructive

Replace the stored message turn history for a conversation using PATCH /agents/{agentId}/convos/{convoId}/messages. This overwrites voiceglow/{agentId}/convos/{convoId}/convo/JSON_STRING with the provided turns array. Set updateConversationMetadata=true (default) to also refresh messagesNum, lastMessage, firstMessageTS, lastMessageTS, and lastModified on the light conversation doc. Because this is a full replacement, confirmReplace must be true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>",
      "convoId": "<convoId>",
      "turns": "<turns>",
      "confirmReplace": "<confirmReplace>"
    },
    "name": "update_conversation_messages"
  }
}

Input Schema

Name	Required	Description
`turns`	Yes	Complete replacement turn history. Each turn requires from + messages. This array becomes the stored transcript history.
`agentId`	Yes	The agent ID.
`convoId`	Yes	The conversation ID.
`lgMessages`	No	Optional LangGraph/langchain message array passthrough.
`confirmReplace`	Yes	Must be true because this replaces the stored conversation message history.
`updateConversationMetadata`	No	Default true. Refreshes messagesNum, lastMessage, firstMessageTS, lastMessageTS, and lastModified on the light conversation document.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes further: it names the exact storage path overwritten, states that the supplied `turns` array becomes the stored transcript, and discloses the side effect of refreshing messagesNum, lastMessage, firstMessageTS, lastMessageTS, and lastModified on the light conversation doc. That is real behavioral context an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then the overwrite target, then metadata side effects and the confirm guard. Dense and largely waste-free, though the raw storage path is somewhat internal plumbing that costs a clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent replacement tool, the description covers the destructive scope, the guard parameter, and the secondary metadata mutation. With annotations already covering the safety profile and a fully documented schema, nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds consequence-level meaning: `turns` is a complete replacement (not a merge), `updateConversationMetadata` defaults true and enumerates exactly which fields it touches, and `confirmReplace` is a mandatory safety gate. It reinforces rather than merely restates the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: "Replace the stored message turn history for a conversation," and pins the endpoint. That is clearly distinct from siblings like update_conversation or add_conversation_note, but the description never names those alternatives, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The full-replacement framing implies when this applies (rewriting an entire transcript rather than appending), and the confirmReplace requirement is stated. However, there is no explicit "use X instead when..." guidance against update_conversation, add_conversation_note, or delete_conversation, so the usage boundary is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Convocore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?