Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_read_message

Read-only

Read a full Gmail message by ID to retrieve headers, plain-text body, and attachment list with IDs.

Instructions

Read a full email: headers, plain-text body, and attachment list (with attachmentIds).

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": "gmail_read_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful return-shape detail (plain-text body, attachment list with attachmentIds, which implies attachment content is not included and must be fetched separately), but it does not mention pagination, behavior on HTML-only messages, or size limits.

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?

One sentence with zero filler, front-loading the verb and resource followed by the enumerated contents. 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with annotation coverage, the definition is nearly adequate because it describes the return shape in the absence of an output schema. The remaining gap is the input side: an agent is never told what a valid messageId looks like or which sibling produces one.

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?

The single messageId parameter has 0% schema description coverage, and the description says nothing about its format or where to obtain it. The only hint is the parenthetical attachmentIds, which refers to output rather than the input parameter, so the description does not compensate for the coverage gap.

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 (read) and resource (a full email) and enumerates the returned components: headers, plain-text body, and attachment list with attachmentIds. It implicitly separates itself from gmail_read_thread by scoping to a single 'email' rather than a thread, but never names the sibling to make the distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the name and the word 'full' – the agent can infer this is the way to get complete message content rather than a search snippet. There is no statement of when to prefer gmail_read_thread, no prerequisite that a messageId comes from gmail_search, and no exclusions.

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