Skip to main content
Glama

Update conversations in bulk

update_conversations
DestructiveIdempotent

Use this when the user wants the same change made to several email conversations at once: marked read or unread, starred or not, or moved to Archived, Spam or Trash or back to the inbox. Applies one change to 1 to 50 email conversations, at the mail provider too, and reports each one's outcome. LinkedIn chats cannot be changed in bulk. 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": {
      "conversationIds": "<conversationIds>"
    },
    "name": "update_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
isReadNoMarks every message read, or with false unread.
isSpamNoMoves it to Spam, or with false back to the inbox.
isDeletedNoMoves it to Trash, or with false back to the inbox.
isArchivedNoMoves it to Archived, or with false back to the inbox.
isFavoriteNoStars the conversation, or with false takes the star off.
conversationIdsYes1 to 50 email conversations, each once, by `id`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses non-obvious behavior: the change is propagated 'at the mail provider too', the batch is capped at 1–50, per-item outcomes are reported, and the call is free. It does not say whether Trash moves are permanent or how partial failures are surfaced, but it adds real context the annotations don't carry.

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?

Four tight sentences, front-loaded with the use case, followed by scale, side effects, and the LinkedIn caveat. The one-word 'Free.' is a fragment but delivers a distinct and useful cost fact, so little is wasted.

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?

With no output schema, the description usefully covers the return shape at a high level ('reports each one's outcome') and states the batch bound and external propagation. Remaining gaps – permanence of Trash deletion and partial-failure behavior – are minor for a mutation tool whose annotations already flag destructiveness.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents the true/false semantics of each boolean flag, so the description's enumeration of read/star/archive/spam/trash mostly restates the schema. 'Applies one change' slightly understates that the schema accepts several boolean flags simultaneously, adding a small ambiguity rather than meaning.

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?

States a specific verb (bulk update) plus the resource (email conversations) and enumerates the exact mutations: read/unread, starred, Archived/Spam/Trash/inbox. The phrase 'several ... at once' and '1 to 50' implicitly separates it from the singular update_conversation sibling, but that sibling is never named, so the differentiation is inferred rather than explicit.

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?

Opens with an explicit when-to-use trigger ('when the user wants the same change made to several email conversations at once') and gives a firm exclusion ('LinkedIn chats cannot be changed in bulk'). It stops short of routing the agent to update_conversation for the single-conversation case, so it lacks explicit alternatives.

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