Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

gmail_messages_get

Read-only

Retrieve a single Gmail message by ID to inspect its content, metadata, or raw format for a specified user.

Instructions

Get a single 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": {
      "userId": "<userId>",
      "id": "<id>"
    },
    "name": "gmail_messages_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage ID
formatNoResponse format: full, metadata, minimal, raw
userIdYesUser ID (use 'me')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing beyond them: no note on behavior when the ID is invalid, no mention of permission/scope requirements, and no hint that the format parameter changes payload size and cost.

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 waste. It is efficient, though its brevity edges toward under-specification rather than maximal usefulness.

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-only fetch with full schema coverage and annotations, the description is adequate to invoke the tool correctly. It omits the default response format and any pointer to format choice, which would help an agent avoid fetching more data than needed.

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%, with all three parameters documented including the 'me' hint and the accepted format values, so the schema does the heavy lifting. The description contributes no additional semantics such as default format or the tradeoffs between full, metadata, minimal, and raw.

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 and resource ('Get a single Gmail message by ID'), which is enough to separate it from the list operation implied by the sibling gmail_messages_list. It does not explicitly contrast itself with gmail_threads_get, so it falls short of full sibling differentiation.

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 guidance on when to choose this over gmail_threads_get or gmail_messages_list, and no mention of prerequisites or error cases for unknown IDs. Usage is only implied by the phrase 'single ... by ID'.

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