Skip to main content
Glama

update_conversation

Idempotent

Organise a DM thread: pin or unpin it, archive or restore it, set its tags, and/or mark it read. Omit what you don't want to change.

tags REPLACES the thread's whole tag list (read it first with get_conversation and send the full list back) — up to 8 tags, each lowercased with spaces turned into dashes and cut at 24 characters. The tag "hot-lead" is what the inbox's "hot" filter shows. Archiving unpins. A new message from the person brings an archived thread back by itself.

Nothing is sent to the person. Needs the DM permission (reeldrop:automations).

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": {
      "workspace_id": "<workspace_id>",
      "conversation_id": "<conversation_id>"
    },
    "name": "update_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
pinnedNo
archivedNo
mark_readNo
workspace_idYes
conversation_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
tabYes
nameNo
tagsYes
emailNo
igsidYes
phoneNo
pinnedYes
archivedYes
usernameNo
can_replyYes
unread_countYes
last_message_atYes
last_message_previewYes
reply_window_ends_atNo
last_message_directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses that nothing is sent to the recipient, that archiving implicitly unpins, that an incoming message auto-restores an archived thread, the tag normalization rules (lowercase, dashes, 24-char cut, max 8), the meaning of 'hot-lead', and the required reeldrop:automations permission. This is exactly the kind of side-effect and prerequisite context annotations cannot carry.

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

Conciseness5/5

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

The action list is front-loaded in the first sentence, followed by the highest-risk detail (tags replacement), then edge behaviors, then permissions. Every sentence carries information an agent would otherwise have to guess.

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 six-parameter mutation tool with an output schema already covering return values, the description supplies the missing pieces: destructive-vs-benign side effects, tag replacement semantics, permission requirements, and automatic state transitions. Nothing an agent needs to invoke it correctly appears absent.

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?

With 0% schema description coverage, the description compensates well: it explains that tags REPLACES the entire list (with normalization and size limits), clarifies that archived and pinned are toggle-style booleans, and that mark_read is an action flag. workspace_id and conversation_id are left undocumented, though their meaning is self-evident.

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

Purpose5/5

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

The description opens with a concrete verb and resource ('Organise a DM thread') and enumerates the exact sub-operations: pin/unpin, archive/restore, set tags, mark read. This cleanly separates it from siblings like get_conversation and reply_to_conversation, which read or send rather than modify thread state.

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

Usage Guidelines4/5

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

It gives a clear operating rule ('Omit what you don't want to change') and explicitly routes tag updates through get_conversation first, which is genuine when-to-use guidance. It does not explicitly state when not to use it versus reply_to_conversation, but the mutation-only scope makes that boundary fairly obvious.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources