Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

list_email_attachments

Find and list file attachments from emails that match a given subject keyword, helping you quickly locate attachments without manually searching each email.

Instructions

List attachments for emails matching a subject keyword.

Args: account: Account name (e.g., "Gmail", "Work", "Personal") subject_keyword: Keyword to search for in email subjects max_results: Maximum number of matching emails to check (default: 1)

Returns: List of attachments with their names and sizes

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

Input Schema

Name	Required	Description	Default
`account`	Yes
`max_results`	No
`subject_keyword`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.6.1Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It states the return type (list of attachments with names and sizes) but omits behavioral traits such as whether it is read-only, if it only checks max_results emails, or what happens on no matches.

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 short and structured with Args and Returns sections. Every sentence provides value; no superfluous text.

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?

Given the presence of an output schema and 3 parameters, the description is adequate but not thorough. It covers basic functionality and return format but lacks usage guidance and behavioral details.

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 has no descriptions (0% coverage), but the description's Args section adds meaning: examples for account (e.g., 'Gmail'), explanation of max_results ('Maximum number of matching emails to check'), and clarifies the purpose of subject_keyword.

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 description clearly states 'List attachments for emails matching a subject keyword' with a specific verb and resource. It effectively conveys the tool's function but does not explicitly differentiate from sibling tools like search_emails or get_email_with_content.

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

Usage Guidelines2/5

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

The description does not specify when to use this tool versus alternatives. It lacks explicit guidance on usage context, prerequisites, or exclusions, leaving the agent to infer from the parameter list alone.

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