Skip to main content
Glama
gmail-mcp
by gchallen

get_message

Read-only

Read a Gmail message by ID to retrieve headers, labels, attachment list, and body; use for received messages, not drafts.

Instructions

Read one message by ID: headers, labels, attachment list and body. Not for drafts; use get_draft for those.

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": {
      "messageId": "<messageId>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoWhich fields to return. "plain_text" (default): headers, snippet, labels, attachments list and the text body (HTML converted to text when there is no text part). "full": plain_text plus htmlBody. "minimal": headers, snippet and labels only, no body. "metadata": like minimal but without subject or snippet. "raw": the RFC 822 source.
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond that by disclosing the returned content shape (headers, labels, attachment list, body) in the absence of an output schema. It does not mention error behavior for a missing ID or any permission constraints, which keeps it below a 5.

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?

Two short sentences with zero filler; the primary purpose and the returned payload are front-loaded before the exclusion clause. Nothing could be removed without losing information.

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 two-parameter read tool with no output schema, the description covers purpose, routing and returned fields, and the format enum documents response variants thoroughly. Only minor gaps remain, such as what happens when the ID does not exist or is inaccessible.

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 50%: the 'format' enum carries a detailed per-value explanation, while 'messageId' is undocumented but self-evident from 'by ID' in the description. The description itself adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Read one message by ID') and immediately enumerates the payload ('headers, labels, attachment list and body'), so the agent knows exactly what it gets. It also names the sibling it is not (get_draft), making it distinguishable without opening 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 an explicit exclusion plus the alternative to use instead ('Not for drafts; use get_draft for those'), which is real routing guidance. It stops short of covering other adjacent cases (e.g., fetching a whole conversation via get_thread) or when to prefer one over the other, so it is clear but not exhaustive.

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