Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_thread_get

Fetches all messages in a Gmail thread using an account and thread ID, letting you review the complete conversation in one call.

Instructions

Fetch a whole thread (all messages).

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

Input Schema

NameRequiredDescriptionDefault
accountYes
thread_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states it fetches all messages but does not disclose pagination, formatting, authentication requirements, rate limits, or return structure. Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise single sentence, but it is too minimal. While it has no fluff, it lacks necessary detail to be informative. Could benefit from more context without sacrificing conciseness.

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

Completeness2/5

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

No output schema, so description should explain return values. It says 'all messages' but is vague on structure (e.g., includes subject, body, attachments). Incomplete for a fetch tool with no other documentation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the two parameters (account and thread_id). No format hints or examples provided. The description adds no value beyond the schema.

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 'Fetch a whole thread (all messages)' clearly states the verb (Fetch), resource (thread), and scope (all messages). It distinguishes itself from siblings like gmail_message_get (single message) and gmail_search (search threads).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., gmail_message_get for a single message). No context about prerequisites or scenarios. The description is too brief to provide usage guidance.

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

Deploy Server

Other Tools