Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_read_thread

Read-only

Reads every message in a Gmail email thread in order, so you can follow a full conversation from the first reply to the latest without opening each email separately.

Instructions

Read every message in an email thread/conversation in order.

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": {
      "threadId": "<threadId>"
    },
    "name": "gmail_read_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/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 safety and external-data exposure are covered. The description adds one real behavioral fact — messages come back 'in order' — but says nothing about whether all messages are guaranteed returned, what fields each message carries, or how large threads are handled.

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?

One short sentence with zero waste; the resource and the ordering guarantee are both front-loaded. Nothing is repeated from the schema or annotations.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with no output schema, the description covers the core action adequately, and annotations carry the safety profile. However, it omits the return shape (headers, bodies, attachments per message) and the provenance of threadId, which an agent needs to call this correctly the first time.

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

Parameters2/5

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

The single threadId parameter has 0% schema description coverage, and the description does not explain what a thread ID looks like or where to obtain it (e.g., from gmail_search results). It only implies the parameter's meaning through the word 'thread', leaving the agent to infer format and source.

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?

Specific verb (Read) plus resource (every message in an email thread/conversation), with the scope 'every message' implicitly distinguishing it from the single-message sibling gmail_read_message. The sibling is not named explicitly, so an agent must infer the split from scope wording alone.

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?

Use case is implied by 'thread/conversation' — reach for it when the whole exchange matters rather than one message — but there is no explicit when-to-use, when-not-to-use, or named alternative such as gmail_read_message for single-message reads.

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