Skip to main content
Glama

gmail_read

Read-onlyIdempotent

Read a Gmail message by ID to retrieve email content in minimal, metadata, full, or raw format.

Instructions

Read a Gmail message by id.

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": {
      "message_id": "<message_id>"
    },
    "name": "gmail_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoGmail response format (default metadata)
message_idYesGmail message id
access_tokenNoGmail access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — no note that the 'raw' format returns base64-encoded RFC822 content or that access_token must be valid — but since it contradicts nothing and annotations carry the burden, a minimum-viable 3 applies.

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 front-loaded sentence with zero filler and no wasted clauses. It is efficient, though the extreme terseness edges toward under-specification rather than optimal density.

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 complete annotations and fully documented parameters, the only meaningful gap is the absent output schema combined with no statement of what a read returns (headers only, body, attachment metadata) or how 'format' changes the response shape. Usable, but not self-sufficient.

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%, including the format enum and default, so the description has little to add; 'by id' merely restates the required message_id parameter. Baseline 3 is appropriate when the schema documents all three parameters.

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 (read), resource (Gmail message) and selector (by id), which cleanly separates it from gmail_search and gmail_send in the sibling list. It is clear but does not explicitly name the sibling it is not, so it falls short of a 5.

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?

The phrase 'by id' implies the prerequisite of a previously obtained id, but the description never says when to use this versus gmail_search or what to do if the id is unknown. No explicit when-to-use or exclusion guidance is given.

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