Skip to main content
Glama
wylieswanson

apple-mail-mcp-server

by wylieswanson

get_attachment_content

Read-onlyIdempotent

Read an attachment's content inline without writing to disk, enabling inspection of text files, JSON, or small PDFs before deciding next steps.

Instructions

Read one attachment's content inline, without writing it to disk.

For "triage" workflows where you want to inspect an attachment (a text file, JSON, a small PDF) before deciding what to do with it — instead of save_attachments → read the file → clean up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoMail.app account name or UUID. Supply it (with ``mailbox``) to use the faster IMAP path; pass the same value you read the message with so the attachment ordering matches.
mailboxNoFolder the message lives in (for the IMAP path).
message_idYesMessage id, as returned by ``search_messages`` / ``get_messages`` (RFC 5322 Message-ID on the IMAP path, Mail's internal id on the AppleScript path).
attachment_indexYes0-based index into the message's attachments, in the same order ``get_attachments`` / ``get_messages`` (``include_attachments=True``) report them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds context by clarifying no disk write, and hints at supported file types (text, JSON, small PDFs), but could be more explicit about limitations (e.g., size constraints).

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?

Two short paragraphs with no extraneous content. The key purpose and usage scenario are front-loaded, and every sentence provides essential information.

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?

Given the presence of an output schema and annotations, the description adequately covers usage context, behavioral traits, and parameter semantics, leaving no significant gaps for a read operation.

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?

Schema coverage is 100%, but the description adds value by explaining the rationale for account/mailbox (faster IMAP path) and linking attachment_index to sibling tool output, which helps the agent understand parameter relationships.

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 explicitly states the action (read content) and resource (attachment), and distinguishes itself by emphasizing 'inline, without writing to disk.' This clearly separates it from sibling tools like save_attachments.

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 a concrete use-case ('triage' workflows) and explicitly contrasts with the alternative workflow of save_attachments + read + cleanup, making it clear when to choose this tool.

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/wylieswanson/apple-mail-pz-mcp'

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