Skip to main content
Glama

graph_read_mail

Retrieve full details of a specific email by message ID, choosing HTML or text body format and optionally using immutable IDs or a shared mailbox.

Instructions

Read full details of a specific email.

Args: message_id: The email message ID. body_type: Body format to request: "html" or "text" (default "html"). Use "text" to avoid pulling large HTML bodies into context. immutable_ids: Whether to ask Graph for immutable message IDs (default false). A message ID changes when the message is moved, so a stored ID stops working; an immutable ID survives the move. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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

Input Schema

NameRequiredDescriptionDefault
mailboxNo
body_typeNohtml
message_idYes
immutable_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains the immutable_ids caveat (a message ID changes when the message is moved, so stored IDs break), discloses the shared-mailbox permission requirement, and warns about large HTML bodies. The main undisclosed behavior is whether reading marks the message as read, which matters given the separate graph_mark_mail_read sibling exists.

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?

Structure is front-loaded and easy to scan: a one-line purpose followed by a per-parameter Args block. The content is dense but each parameter note adds operational value; only minor redundancy exists in restating defaults that already live in the schema.

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 read tool with no annotations and no output schema, the description covers inputs thoroughly but says nothing about what the response contains (headers, attachments, body shape) or how large payloads are returned. The absence of any return-shape hint leaves a real gap for an agent deciding between 'html' and 'text'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it does: all four parameters are explained with meaning beyond types and defaults, including the semantic consequence of immutable_ids, the context-cost tradeoff of body_type, and the targeting semantics of mailbox (empty = own mailbox). This is exactly what a 0%-coverage schema requires.

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?

The opening line states a specific verb and resource: "Read full details of a specific email," which is clearly distinct from list/search siblings by scope (one message vs. many). It stops short of naming an alternative such as graph_list_mail or graph_search_mail, so sibling disambiguation is left partly to inference.

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?

There is embedded usage guidance for individual params ("Use 'text' to avoid pulling large HTML bodies into context", and mailbox "Requires the delegated Mail.*.Shared permissions"), which is genuinely actionable. However, there is no explicit statement of when to call this versus graph_search_mail or graph_list_mail, and no prerequisites section at the tool level.

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