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

Google Workspace (GWS) MCP Server

gmail_threads_get

Read-only

Retrieve a full Gmail thread by ID to read every message in a conversation. Use it to follow email discussions and gather complete context in one call.

Instructions

Get a full Gmail thread by ID (all messages in the conversation).

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThread ID
formatNoResponse format: full, metadata, minimal
userIdYesUser ID (use 'me')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the response spans every message in the conversation, which is useful, but says nothing about behavior under the alternate formats or what happens with an invalid/expired thread ID.

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?

A single sentence with the resource and scope front-loaded and no filler. It is efficient, though the parenthetical could carry slightly more decision-relevant detail without losing brevity.

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 simple three-parameter read tool with full schema coverage and passing annotations, this is largely sufficient: the agent knows it retrieves an entire conversation by ID. The only real gap is the unstated effect of the 'format' option, which the schema partially covers.

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%, so all three parameters are already documented in the schema, including the 'me' convention and the full/metadata/minimal formats. The description adds only the notion that the ID is a thread ID and that the default is a full thread; it does not clarify how 'format' changes output.

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 and resource ('Get a full Gmail thread by ID') and clarifies the return scope with '(all messages in the conversation)'. This distinguishes it from a single-message fetch or a thread listing, though it never names those siblings explicitly.

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?

Usage is implied: fetch an entire conversation when you have a thread ID. There is no explicit guidance on when to prefer gmail_messages_get for a single message or gmail_threads_list for enumeration, and the 'format' trade-offs are not discussed.

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