Skip to main content
Glama
Sign In
Apple Mail MCP Server

Apple Mail MCP Server

by isityael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_email_with_content

Search emails by subject keyword and retrieve full content previews from your Apple Mail accounts.

Instructions

Search for emails by subject keyword and return with full content preview.

Args: account: Account name to search in (e.g., "Gmail", "Work") subject_keyword: Keyword to search for in email subjects max_results: Maximum number of matching emails to return (default: 5) max_content_length: Maximum content length in characters (default: 300, 0 = unlimited) mailbox: Mailbox to search (default: "INBOX", use "All" for all mailboxes)

Returns: Detailed email information including content preview

User Preferences: {"workflow": "default", "notifications": "enabled"}

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>",
      "subject_keyword": "<subject_keyword>"
    },
    "name": "get_email_with_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
mailboxNoINBOX
max_resultsNo
subject_keywordYes
max_content_lengthNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.6.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description only states the basic operation. It does not disclose potential side effects (none expected as read-only), authentication requirements, rate limits, or error conditions.

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?

The description is front-loaded with a concise summary followed by a well-structured parameter list. It avoids unnecessary text but could be slightly more compact by not repeating defaults that are already in the schema.

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?

The description explains all parameters and indicates the return type (detailed email info with content preview). With an output schema present, further detail on return values is not needed. Missing edge cases like empty results or errors.

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?

With 0% schema coverage, the description adds essential meaning for all 5 parameters, including examples, defaults, and special values (e.g., 'use "All" for all mailboxes'). This fully compensates for the schema's lack of descriptions.

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 states the specific action 'Search for emails by subject keyword' and the output 'full content preview'. This clearly distinguishes it from sibling tools like search_emails (broader) or search_by_sender.

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 description implies usage for subject keyword searches but does not provide explicit guidance on when to use vs alternatives or when not to use. No alternatives or exclusions are mentioned.

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