apple-mail-mcp

by jayvee6

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

move_email

Move an email to a specified mailbox in Apple Mail. Use list_folders to see available destination mailboxes.

Instructions

Move an email to a different mailbox. Use list_folders to see available mailbox names.

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": {
      "message_ref": "<message_ref>",
      "dest_account": "<dest_account>",
      "dest_mailbox": "<dest_mailbox>"
    },
    "name": "move_email"
  }
}

Input Schema

Name	Required	Description
`message_ref`	Yes	Composite message reference from list_emails or search_emails.
`dest_account`	Yes	Destination account name, e.g. "iCloud".
`dest_mailbox`	Yes	Destination mailbox name, e.g. "Finance & Accounts". Must match exactly (case-sensitive).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 4, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the core action without revealing side effects (e.g., whether the email is removed from the source mailbox, reversibility, or permission requirements). This is a significant gap for a mutation tool.

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 extremely concise: two short sentences with the action front-loaded. Every word earns its place, and it includes a practical hint without unnecessary fluff.

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?

For a simple tool with fully documented parameters and no output schema, the description is minimally adequate. However, it lacks information about return values, error conditions, or side effects, and does not differentiate from similar sibling tools. Given the lack of annotations, more context would improve completeness.

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 100%, so the parameters are already well-documented in the schema. The description adds minor value by advising use of list_folders to discover destination mailbox names, but it does not enhance parameter semantics beyond that.

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 states a clear action ('Move an email to a different mailbox') with a specific resource (email) and destination (mailbox). It does not explicitly distinguish from sibling tools like move_to_junk or archive_email, but is clear enough to stand alone.

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 when to use the tool (when an email needs to be moved), and it provides a useful pointer to list_folders for finding mailbox names. However, it does not explicitly state when not to use it or how it differs from alternatives like move_to_junk or archive_email.

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