Skip to main content
Glama
androidua

Apple Mail MCP Server

by androidua

mail_read_email

Read-onlyIdempotent

Retrieve the full content of an Apple Mail email using its ID from search results. Get subject, sender, recipients, date, read status, and body text.

Instructions

Read the full content of a specific Apple Mail email by its ID.

Decodes the opaque email_id produced by mail_search_emails, locates the message in Apple Mail, and returns its complete content: subject, sender, recipients (To, CC), date received, read-status, and full body text.

Strictly read-only — the message read-status is NOT changed by this call.

Args: params (ReadEmailInput): Input containing: - email_id (str): Opaque ID from mail_search_emails. Required. - response_format (str): 'markdown' (default) or 'json'.

Returns: str: Full email content.

Markdown example:
    # Email: Invoice for March

    - **From**: billing@example.com
    - **To**: you@icloud.com
    - **CC**: (none)
    - **Date**: Monday, 3 March 2025 at 09:14:02
    - **Read**: Yes
    - **Mailbox**: iCloud / INBOX

    ## Body

    Hi there, please find your invoice attached...

JSON example:
    {
      "subject": "Invoice for March",
      "sender": "billing@example.com",
      "to": "you@icloud.com",
      "cc": "",
      "date": "Monday, 3 March 2025 at 09:14:02",
      "read": true,
      "account": "iCloud",
      "mailbox": "INBOX",
      "body": "Hi there, please find your invoice attached..."
    }

Examples: - Use when: "Read the email about invoices" (after searching) → pass the email_id from search results - Don't use when: You don't have an email_id yet → use mail_search_emails first

Error Handling: - Returns an error if the email_id is malformed or expired. - Returns an error if the message cannot be found (e.g. deleted since search). - Returns an error if Mail.app cannot be reached. - Reads on very large mailboxes (>30k messages) can take up to a minute; the mailbox is rescanned per read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds that the message read-status is NOT changed, provides performance caveats for large mailboxes, and explains error conditions, all beyond what annotations provide.

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?

The description is well-structured with clear sections (purpose, args, returns, examples, error handling, notes). It is thorough yet concise, with no unnecessary content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a read tool with detailed input schema and annotations, the description is complete: it covers purpose, parameters, return format with examples, error handling, and performance notes. No gaps are apparent.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has detailed descriptions for both parameters, so schema coverage is high. The description reiterates these but adds value through examples of return formats and usage context, justifying a score above baseline.

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?

The description clearly states it reads the full content of a specific Apple Mail email by its ID, using the verb 'Read' and specifying the resource. It distinguishes from sibling tools by noting that mail_search_emails provides the ID needed for this tool.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: use after searching with mail_search_emails, and not without an email_id. It includes examples and a clear 'Don't use when' section, which helps the agent decide correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/androidua/apple-mail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server