Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

delete_account

Destructive

Delete a mail account from Apple Mail by providing its display name or UUID. Removes the account configuration entirely.

Instructions

Delete a mail account from Mail.app.

Removes the account entirely from Mail.app. Use the account UUID (from list_accounts) for stability across renames.

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

Input Schema

Name	Required	Description	Default
`account`	Yes	Account display name (e.g., "Gmail") or UUID.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.2Aug 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds context beyond the destructiveHint annotation by specifying 'Removes the account entirely,' and it warns about the stability issue with display names. This provides useful behavioral expectations for a destructive operation.

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 concise sentences, purpose first, then a practical tip. No fluff.

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?

Given the one parameter, the destructive nature is stated, and the output schema is present, the description covers the essential information for an agent to invoke this tool correctly. It could mention prerequisites or side effects, but it's sufficient for this simple deletion.

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 already describes the 'account' parameter as display name or UUID, but the description adds guidance to prefer UUID for stability, which is not in the schema. This enriches the semantics.

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 'Delete a mail account from Mail.app.' and 'Removes the account entirely from Mail.app.' This is specific to accounts, distinguishing it from sibling delete tools like delete_rule or delete_mailbox. The verb and resource are explicit.

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 does not explicitly contrast with alternatives, but it provides a usage tip: 'Use the account UUID (from list_accounts) for stability across renames.' This suggests when to use this tool is for deleting accounts, but it doesn't say when not to use it or mention alternatives. It's adequate but not explicit.

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