Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

gmail_threads_modify

Idempotent

Modify Gmail thread labels to archive, mark read, or star messages by adding or removing label IDs such as INBOX, UNREAD, and STARRED.

Instructions

Modify a Gmail thread: add/remove labels. To archive, remove INBOX. To mark read, remove UNREAD. To star, add STARRED.

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": {
      "userId": "<userId>",
      "id": "<id>"
    },
    "name": "gmail_threads_modify"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThread ID
userIdYesUser ID (use 'me')
addLabelIdsNoJSON array of label IDs to add, e.g. ["STARRED"]
removeLabelIdsNoJSON array of label IDs to remove, e.g. ["INBOX","UNREAD"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — removing INBOX is what performs an archive — but says nothing about permission requirements, error behavior, or the effect of removing labels that aren't present.

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 short sentences, front-loaded with the core action, then immediately usable recipes. There is no filler and every clause carries operational meaning.

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 a four-parameter, single-purpose mutation tool with full annotation coverage and full schema coverage, the description supplies what is needed to call it correctly. No output schema exists, but the return value of a label modify is incidental; only minor gaps remain around failure behavior and label-ID discovery.

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 parameter documentation is already handled and the baseline would be 3. The description earns a bump by explaining the semantic meaning of specific label IDs (INBOX, UNREAD, STARRED), which the schema only describes generically as "JSON array of label IDs to add/remove."

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?

The description leads with a specific verb and resource ("Modify a Gmail thread") and narrows the scope to label add/remove operations, which is unambiguous. It does not explicitly contrast with gmail_threads_get or gmail_threads_list, but the read-vs-modify distinction is clear from the verb.

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 goes beyond stating context by mapping common goals to concrete parameter actions: archive = remove INBOX, mark read = remove UNREAD, star = add STARRED. That is actionable when-to-use guidance for the most frequent tasks, though it gives no exclusions or prerequisites (e.g., authentication scope or what to do for thread-level vs message-level operations).

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