Skip to main content
Glama
Sign In
Apple Mail MCP

Apple Mail MCP

by cyberprive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_thread

Read-only

Retrieve the full body and metadata for a specific Apple Mail message using its account, mailbox, and numeric message ID from search results.

Instructions

Fetch the full content for a single message.

v1 returns one message (no thread reconstruction). For triage this is sufficient; full threading lands in v1.5.

Args: account: Account name. mailbox: Mailbox name (from search_messages output). id: Mail.app numeric message id (from search_messages output).

Returns {messages: [{id, message_id, account, mailbox, subject, sender, to, cc, date_received, date_sent, read, body}]}.

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": {
      "account": "<account>",
      "mailbox": "<mailbox>",
      "id": "<id>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
accountYes
mailboxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, but the description adds real behavior context: the v1 single-message limitation and the fact that the full body is returned. Usefully labeled as "v1" rather than a bug. It stays silent on body size/truncation limits, which is the main remaining unknown.

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?

Front-loaded purpose, then the version limitation, then args and return shape in a compact block. The Args: section is mostly title restatement, but no sentence is actively wasteful.

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?

There is no output schema, yet the description declares the exact return shape including all message fields, and it discloses the single-message limitation up front. Combined with readOnlyHint, an agent has enough to call this correctly without surprises.

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 carries the full burden. It does add provenance for two params ("from search_messages output") and identifies id as a Mail.app numeric message id, which is genuinely useful. But "Account name" and "Mailbox name" merely restate the titles, so the compensation is only partial.

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?

It gives a specific verb and resource ("Fetch the full content for a single message") and immediately resolves the conflict with its own name by stating that v1 does no thread reconstruction. An agent can tell this apart from search_messages, which only supplies ids.

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?

"For triage this is sufficient; full threading lands in v1.5" implies the tool is the right choice for single-message triage and tells the agent not to expect threading. However, no alternative is named for retrieving a whole conversation, and no explicit when-not condition or prerequisite is stated.

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