Skip to main content
Glama
gmail-mcp-server

gmail-mcp-server

by fbassas

read_email

Retrieve a Gmail message's full content by message ID to review or process a specific email.

Instructions

Llegeix el contingut complet d'un correu pel seu ID de missatge.

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

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full disclosure burden, yet it only restates that the tool reads content. It is silent on a significant side effect for mail tools (whether reading marks the message as read/unread), on permissions required, and on whether attachments or HTML parts are included. Without annotations, this leaves the agent guessing about side effects of an otherwise safe-looking call.

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 economical sentence with the resource and selector front-loaded and no filler. It could have used one more short clause on return shape without hurting brevity, but nothing in it is wasted.

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?

The tool is simple (one required parameter, no output schema, no nesting), and the description covers the core action. However, with no output schema the description should indicate what the 'full content' consists of (body only, headers, attachments) and the read side effect; these gaps matter more because nothing else in the definition supplies them.

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% and the schema only types messageId as a string, so the description must supply meaning. It does identify the parameter as a message ID, but adds no format expectations (e.g., RFC Message-ID header vs. provider-internal opaque ID), which is a meaningful ambiguity when the schema is bare.

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 ('Llegeix el contingut complet d'un correu') plus the key selector ('pel seu ID de missatge'), so the agent knows it returns full message bodies rather than summaries or lists. It does not explicitly name how it differs from search_emails, but the 'full content by ID' framing is naturally distinct from searching.

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?

The phrase 'pel seu ID de missatge' implies a two-step flow (find the ID first, then read), which is useful implicit guidance. However, there is no explicit statement of when to prefer this over search_emails, no prerequisite note about needing a valid ID, and no guidance on error behavior for an unknown ID.

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