Skip to main content
Glama

gmail get message

gmail_get_message
Read-onlyIdempotent

Fetch a single Gmail message with headers and a truncated plain-text body to inspect a specific email while limiting returned content.

Instructions

Fetch one message with headers and a truncated plain-text body.

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_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
body_charsNo
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the body is truncated plain-text, not the full MIME payload — but does not say what is dropped (HTML parts, attachments) or how truncation is controlled.

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 no filler, well matched to a tool that has an output schema. It is terse to the point of omitting the one clause (body_chars/truncation control) that would have paid for itself.

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?

An output schema exists, so return values need no explanation, and the annotations cover the read-only profile. However, with zero schema description coverage on body_chars and message_id, the description leaves an agent guessing about the one parameter that changes behavior.

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?

Schema description coverage is 0%, so the description carries the full burden for both parameters. It hints at truncation but never explains that body_chars (default 4000) sets the truncation length, nor what format message_id takes.

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?

Uses a specific verb ('Fetch') with a specific resource ('one message') and states what is returned (headers plus truncated plain-text body), which separates it from gmail_search_messages and gmail_list_threads. It stops short of naming an alternative for retrieval by ID.

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?

There is no statement of when to use this versus siblings such as gmail_search_messages (to find a message) or gmail_list_threads (to read a conversation). The agent must infer that this is the by-ID retrieval path from the required message_id alone.

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