Skip to main content
Glama
Sign In
Apple Mail MCP

Apple Mail MCP

by jenyago
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_inboxes

Read-only

Search all permitted Apple Mail inboxes in one call, returning the first page from each account. Use an empty query to list messages or unread_only to review new mail.

Instructions

Search the inbox of every permitted account in one call: the first page from each.

Empty query lists messages; unread_only=true reviews what is new. Each account is searched separately and a failing account is reported in its own entry without stopping the rest. Accounts skipped for lack of time are in not_reached. To go deeper in one account, call search_messages with that entry's account_id, mailbox_path and next_offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_inboxes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
scan_limitNo
unread_onlyNo
limit_per_accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, non-open-world semantics, and the description adds material behavior the annotations cannot: per-account partial-failure handling ('a failing account is reported in its own entry without stopping the rest') and time-based skipping surfaced via not_reached, plus the pagination handoff through next_offset.

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?

Four short sentences, front-loaded with purpose and scope, followed by usage conditions, failure semantics, and the escalation path. No redundancy or filler.

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 no output schema, the description does useful work explaining return shape (per-account entries, not_reached, next_offset, account_id, mailbox_path). It is nearly complete, though the meaning of limit_per_account versus the first-page constraint is not spelled out.

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 description coverage is 0% across 4 parameters, so the description carries the burden. It explains query (empty lists everything) and unread_only behavior, but says nothing about scan_limit or limit_per_account, leaving half the parameters undocumented in both schema and text.

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 states a specific verb and resource plus scope: 'Search the inbox of every permitted account in one call: the first page from each.' It also differentiates itself from the sibling search_messages by naming it for deeper single-account work, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions ('Empty query lists messages; unread_only=true reviews what is new') and a concrete routing rule to the alternative tool ('To go deeper in one account, call search_messages with that entry's account_id, mailbox_path and next_offset'). Nothing about tool selection is left to inference.

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