Skip to main content
Glama
Sign In
Apple Mail MCP Server

Apple Mail MCP Server

by isityael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_email

Move emails with a specific subject from one mailbox to another, supporting nested mailboxes and optional message ID override.

Instructions

Move email(s) matching a subject keyword from one mailbox to another.

Args: account: Account name (e.g., "Gmail", "Work") subject_keyword: Keyword to search for in email subjects to_mailbox: Destination mailbox name. For nested mailboxes, use "/" separator (e.g., "Projects/Amplify Impact") from_mailbox: Source mailbox name (default: "INBOX") max_moves: Maximum number of emails to move (default: 1, safety limit) message_ids: Exact Apple Mail message ids to move; when provided, subject filtering is ignored

Returns: Confirmation message with details of moved emails

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>",
      "to_mailbox": "<to_mailbox>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
max_movesNo
to_mailboxYes
message_idsNo
from_mailboxNoINBOX
subject_keywordYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.6.1

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses key behaviors: subject keyword matching, nesting separator for mailboxes, safety limit (max_moves default=1), and that message_ids overrides subject filtering. No annotations exist, so description carries the burden well.

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 clear action sentence, followed by structured Args and Returns. It is moderately sized and fairly concise, though could trim some redundancy.

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 6 parameters, no annotations, and many siblings, the description covers core behaviors but lacks usage guidelines and comparison to similar tools. It explains override logic but doesn't address common workflows.

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 description coverage, the Args section provides complete parameter explanations, including defaults, nesting hints, and the override relationship between message_ids and subject_keyword. This adds significant meaning beyond the schema.

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 the action: 'Move email(s) matching a subject keyword from one mailbox to another.' This is specific and differentiates from siblings like 'bulk_move_emails' and 'imap_bulk_move'.

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?

No guidance on when to use this tool versus alternatives like 'delete_emails', 'archive_emails', or 'bulk_move_emails'. The description doesn't mention prerequisites or conditions for use.

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