Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

List Account Addresses

list_account_addresses

Get all configured email addresses for each Mail account to map account names to actual addresses. Use it to identify which inbox received a message by address, not display name.

Instructions

List all configured email addresses for each Mail account.

Useful for mapping a Mail.app account name (e.g. "Gmail", "Work") to the actual email address(es) it receives mail at — handy when an integration needs to know which inbox a message landed in by address rather than by Mail.app's display name.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv3.2.1Oct 20, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / title

Removed value: -"list_account_addressesArguments"

addedOutput schema / additionalProperties

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "additionalProperties": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": "Result",
-    "type": "object"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

removedOutput schema / title

Removed value: -"list_account_addressesOutput"

Addedv3.1.3May 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. "List" implies a read-only operation, but there is no explicit safety statement, no pagination or scoping note. The output schema covers return shape, so the remaining gap is modest, but for a tool with zero annotation coverage this is only adequate.

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?

Front-loaded with the core action in the first sentence, with the rationale following. Slightly verbose in the second sentence but each part earns its place by explaining the practical value.

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 a zero-parameter read tool with an output schema, the description covers what it does and why it's useful. Missing only explicit safety/scope notes, which is minor here since the output schema handles the return contract.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent parameters.

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?

States a specific verb (list) and resource (configured email addresses for each Mail account), and distinguishes itself from the sibling list_accounts by focusing on addresses rather than accounts. An agent can immediately tell what this returns.

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

Usage Guidelines4/5

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

Provides a clear motivating use case — mapping a Mail.app display name like "Gmail" or "Work" to actual addresses for integrations. It doesn't explicitly name when to prefer a sibling (e.g. list_accounts), but the context is clear enough to select it.

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