Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Gmail: Get message

gmail_get_message
Read-only

Retrieve a single Gmail message by ID, including headers and body parts, or request metadata-only headers or the raw RFC822 message for focused processing.

Instructions

[UNIFIED] Get a single Gmail message by id, including headers and (with format=full) the body parts. Use format=metadata for headers only (cheaper) or format=raw for the full RFC822 message.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
formatNofull
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

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, so the safety profile is known; the description adds real value by disclosing that format=full includes body parts, metadata is headers-only and cheaper, and raw returns the full RFC822 message. It does not mention auth requirements or size limits, which keeps it from being 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 sentences, front-loaded with the core action and the return contents, then the format trade-offs. No wasted wording and every clause carries 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 simple read-only single-item fetch with no output schema, the description covers what is fetched and how format changes the result. The one gap is the unexplained required 'site' parameter, which an agent must guess at from the schema alone.

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 0%, so the description must carry the load. It does define the meaningful format values (full, metadata, raw) that the schema leaves as a bare string, but it says nothing about the required 'site' parameter and only implicitly covers message_id.

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 ('Get a single Gmail message by id') plus the returned content (headers, body parts), which clearly separates it from list-oriented siblings like gmail_list_messages and gmail_get_attachment.

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 explicit guidance on choosing the format: format=metadata for headers only (cheaper), format=raw for full RFC822. It does not state when this tool is preferred over gmail_list_messages or gmail_get_attachment, but the format-selection guidance is clear and actionable.

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