gsuite

google-gmail_get_message

Retrieve a Gmail message by its ID, with options for format and metadata headers.

Instructions

Get a specific 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": {
      "id": "<id>"
    },
    "name": "google-gmail_get_message"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Message ID to retrieve
`format`	No	Format of message (full, metadata, minimal, raw)
`userId`	No	User's email address or 'me' for authenticated user
`metadataHeaders`	No	Comma-separated list of header names to include when format=metadata

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must communicate behavioral traits. It only states the basic action, lacking details on side effects, auth requirements, rate limits, or response structure.

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?

Single sentence, no filler, front-loaded with key verb and object.

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?

Given no output schema and simple input, the description should at least mention the return object type or typical usage pattern. It only says 'Get', leaving the agent uninformed about the response.

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 parameters are well-documented in the schema. The description adds no further meaning beyond 'get by ID', but does not detract.

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 'Get a specific message by ID' clearly states the action (get) and resource (message), distinguishing it from siblings that list, delete, modify, or send messages.

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 list_messages or search_messages, nor prerequisites like obtaining the ID first.

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