Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

List Mailboxes

list_mailboxes

Retrieve all mailboxes (folders) across Apple Mail accounts, optionally filtering by account and including message counts for each folder.

Instructions

List all mailboxes (folders) for a specific account or all accounts.

Input Schema

Name	Required	Description	Default
`account`	No	Optional account name to filter (e.g., "Gmail", "Work"). If None, shows all accounts.
`include_counts`	No	Whether to include message counts for each mailbox (default: True)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv3.2.1Oct 20, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / account / description
```
Added value: +"Optional account name to filter (e.g., \"Gmail\", \"Work\"). If None, shows all accounts."
```
- removedInput schema / properties / account / title
```
Removed value: -"Account"
```
- addedInput schema / properties / include_counts / description
```
Added value: +"Whether to include message counts for each mailbox (default: True)"
```
- removedInput schema / properties / include_counts / title
```
Removed value: -"Include Counts"
```
- removedInput schema / title
```
Removed value: -"list_mailboxesArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"list_mailboxesOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
First observedv3.1.0Apr 2, 2026

TDQS

A3.6/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 full behavioral burden. 'List' implies a read-only operation, but it does not state permissions, rate limits, pagination, or that it is non-destructive, leaving meaningful behavioral context unstated.

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 a single front-loaded sentence with no redundant or wasted phrasing. It is appropriately sized for a simple list tool.

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 low complexity, full schema description coverage, and the presence of an output schema, the description provides enough scope information for an agent to call the tool. It is slightly incomplete because it does not mention the include_counts parameter, though the schema covers that.

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 coverage is 100%: both optional parameters have clear descriptions in the schema. The description only echoes the account filtering concept and adds no new semantics beyond what the schema already provides, so this is the baseline score.

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 specific verb and resource ('List all mailboxes (folders)') and a scope ('for a specific account or all accounts'). It is clear, but it does not explicitly differentiate this tool from sibling list tools such as list_accounts or list_inbox_emails beyond the resource name.

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 phrase 'for a specific account or all accounts' implies how to use the optional account filter, but the description gives no explicit when-to-use guidance, exclusions, or alternatives to consider. Usage is only implied.

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