google-workspace-mcp-server

Get Gmail Thread

gmail_get_thread

Read-onlyIdempotent

Retrieve all messages in a Gmail conversation thread by providing the thread ID. Supports markdown or JSON output.

Instructions

Get all messages in a conversation thread.

Args:

thread_id (string): The thread ID to retrieve
response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: All messages in the thread with full content.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "gmail_get_thread"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes	The ID of the thread to retrieve
`response_format`	No	Output format: 'markdown' or 'json'	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already disclose read-only, idempotent, and non-destructive behavior. The description adds that it returns all messages with full content and shows the response_format default, but does not add significant behavioral context beyond that. Given the strong annotation coverage, this is adequate but not outstanding.

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 description is concise and front-loaded with the purpose, followed by a clear Args/Returns structure. Every sentence adds value, with no redundancy or filler.

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 read-only tool with good annotations and full schema coverage, the description is nearly complete. It states the return content and format options. It could mention how to obtain a thread_id or note that large threads may be truncated, but these are not essential for basic usage.

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 description coverage is 100%, so the schema already documents both parameters. The description's Args section restates the schema contents (thread_id, response_format) without adding new meaning or examples, providing no extra semantic value.

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 uses a specific verb and resource: 'Get all messages in a conversation thread.' This clearly distinguishes it from sibling tools like gmail_get_message (single message) and gmail_list_messages (multiple messages across threads).

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?

The description implies when to use the tool (when you need all messages in a thread), providing clear context. However, it does not explicitly mention alternatives or exclusions, such as 'use gmail_get_message for a single message' or 'use gmail_list_messages to search across threads.'

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