Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Mailbox Unread Counts

get_mailbox_unread_counts

Retrieve unread email counts for each mailbox across one or all Apple Mail accounts; optionally summarize to per-account inbox totals.

Instructions

Get unread counts per mailbox for one account or all accounts.

When summary_only=True, returns only per-account inbox unread totals (replaces the former get_unread_count tool).

Input Schema

Name	Required	Description
`account`	No	Optional account name filter
`include_zero`	No	Whether to include mailboxes with zero unread messages
`summary_only`	No	If True, return only per-account inbox unread totals (flat dict of account name -> unread count)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv3.2.1Oct 20, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / account / description
```
Added value: +"Optional account name filter"
```
removedInput schema / properties / account / title
```
Removed value: -"Account"
```

addedInput schema / properties / include_zero / description

Added value: +"Whether to include mailboxes with zero unread messages"

removedInput schema / properties / include_zero / title
```
Removed value: -"Include Zero"
```

addedInput schema / properties / summary_only / description

Added value: +"If True, return only per-account inbox unread totals\n          (flat dict of account name -> unread count)"

removedInput schema / properties / summary_only / title
```
Removed value: -"Summary Only"
```

removedInput schema / title

Removed value: -"get_mailbox_unread_countsArguments"

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "additionalProperties": true,
-    "title": "Result",
-    "type": "object"
-  }
-}

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

removedOutput schema / title

Removed value: -"get_mailbox_unread_countsOutput"

First observedv3.1.0Apr 2, 2026

TDQS

A3.5/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 burden. It usefully discloses the summary_only behavior change and notes it replaces a former tool, but says nothing about read-only safety, freshness of counts, or account-filtering side effects (e.g., unread counts across all accounts by default). Adequate but incomplete for a zero-annotation tool.

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?

Two sentences, front-loaded with the primary purpose before the mode-specific caveat. Efficient, though the parenthetical about the former tool could be trimmed.

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?

With an output schema present, return-value detail is unnecessary, and the description covers scope and the summary_only variant. It leaves the account-filter default behavior and relationship to sibling overview/stats tools implicit, which is a minor gap.

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%, so account and include_zero are already fully documented in the schema. The description adds meaning only for summary_only (flat per-account inbox totals, replacing get_unread_count), which is marginal beyond the schema text. Baseline 3 applies.

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?

States a specific verb and resource ('Get unread counts per mailbox') and clarifies scope ('one account or all accounts'), which separates it from list-oriented siblings. It does not explicitly contrast with close siblings like get_inbox_overview or get_statistics, so it stops short of a 5.

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 it (per-mailbox unread retrieval) and flags the summary_only mode, but gives no explicit guidance on when to prefer this over get_inbox_overview, get_statistics, or inbox_dashboard. Usage is inferable rather than stated.

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