Skip to main content
Glama

gws-mcp__gmail_read_thread

Read-only

Reads a whole Gmail conversation by its thread ID, the threadId that gmail_search, gmail_list and gmail_read return. Answers every message of the thread in one call, in the order they were sent, oldest to newest, drafts and messages in Trash included and marked as such. With depth full, the default, each message carries its from, to, cc, subject and date, the decoded text body, and its attachments with the part IDs gmail_get_attachment takes. With depth headers, each message carries the same headers and Gmail's snippet but no body, which keeps a long conversation small. The bodies of one answer are held to 200,000 characters together: when a thread is longer, the bodies of its oldest messages are left out, and left_out lists those message IDs, each readable in full by gmail_read.

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": "gws-mcp__gmail_read_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNofull (the default): headers, decoded text body and attachments for each message. headers: headers and Gmail's snippet only, no body or attachments.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
thread_idYesThe Gmail thread ID, as threadId in a gmail_search, gmail_list or gmail_read answer
max_body_charsNoCuts each message's body to this many characters, with a truncation marker, before the 200,000 character total is applied. Applies to depth full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial behavior beyond that: messages returned oldest-to-newest, drafts and Trash items included and flagged, a 200,000-character combined body cap, and a left_out list of truncated message IDs. It also clarifies that max_body_chars is applied per message before the total cap, which an agent could not infer elsewhere.

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?

Purpose is front-loaded in the first clause and each subsequent sentence covers a distinct concern (ordering/scope, depth, size limits). Some depth details are repeated from the enum description, so it is slightly longer than strictly necessary.

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

Completeness5/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 carries the return-shape burden and does so: per-message headers, decoded text body, attachments with part IDs usable by gmail_get_attachment, and the left_out field. Nothing an agent needs to invoke or interpret this tool correctly is missing.

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 the baseline is 3. The description does add real meaning about how depth interacts with output size and how max_body_chars composes with the 200,000-character limit, but it does not explain account or thread_id beyond the schema's own wording.

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?

Opens with a specific verb and resource ("Reads a whole Gmail conversation by its thread ID") and scopes it explicitly against single-message reads by noting threadId comes from gmail_search, gmail_list and gmail_read. An agent can distinguish this thread-level reader from gmail_read without inspecting either schema.

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?

Gives concrete selection guidance for the depth enum (full vs. headers for long conversations) and routes the agent to gmail_read when a body was left out due to the size cap. It lacks an explicit statement about when a single-message read is preferable, but the context for choosing is clear.

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.