Skip to main content
Glama

Update a conversation

update_conversation
DestructiveIdempotent

Use this when the user wants one conversation marked read or unread, starred, moved to Archived, Spam or Trash or back to the inbox (one move a call), or its newest received email labelled interested or not interested. The change is made at the mail provider too. A LinkedIn chat can only be marked read. Free.

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": {
      "conversationId": "<conversationId>",
      "channel": "<channel>"
    },
    "name": "update_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoEmail only: `interested` or `not_interested` on the newest email received, or null to take both off.
isReadNoMarks every message read, or with false unread (email only: a LinkedIn chat can only be marked read).
isSpamNoEmail only. Moves it to Spam, or with false back to the inbox.
channelYes`email` or `linkedin`.
isDeletedNoEmail only. Moves it to Trash, or with false back to the inbox.
isArchivedNoEmail only. Moves it to Archived, or with false back to the inbox.
isFavoriteNoEmail only. Stars the conversation, or with false takes the star off.
conversationIdYesThe conversation's `id`, as the conversations list gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, but the description adds real context the agent cannot get from them: the change propagates to the mail provider, moves are mutually exclusive per call, LinkedIn channels support only read marking, and the operation is free. It stops short of describing what a response or failure looks like.

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?

Three tight sentences, front-loaded with the trigger condition, followed by side effects and limits. No filler and no restatement of the title.

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

Completeness4/5

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

For an 8-parameter destructive mutation with no output schema, the description covers triggers, provider-side propagation, mutual exclusivity and channel limits. It could add a note on what happens when conflicting flags are sent or what the call returns, but the essentials for correct invocation are present.

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 a genuinely non-obvious constraint the schema never states: only one move flag (archive/spam/trash) per call. It also repeats the LinkedIn read-only limitation that applies to isRead, reinforcing schema semantics.

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 precise use-case framing and then enumerates the exact mutations (read/unread, star, move to Archived/Spam/Trash/inbox, label interested) on a single conversation. The phrase 'one conversation' implicitly separates it from the bulk sibling update_conversations, and the resource is unambiguous.

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 triggering condition ('when the user wants one conversation marked...') plus operating constraints: 'one move a call' and 'A LinkedIn chat can only be marked read.' It does not explicitly name an alternative tool for bulk edits, so the when-not guidance is left implicit rather than stated.

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