Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

search-messages

Find Apple Mail messages using filters for text, sender, subject, date, read, or flagged status, then get matching IDs for subsequent email operations.

Instructions

Use when: finding messages by query/sender/subject/date/read/flag filters and you need their ids for follow-up operations. Returns: matching messages with id, date, subject, sender, and read state (plus partial-coverage diagnostics when some mailboxes were skipped). Do not use when: you want a plain mailbox listing without filters (use list-messages), already have an id and want the body (use get-message), or want a whole conversation (use get-thread). Prefer this first to obtain the message ids that get-message/mark-as-read/delete-message/move-message and the batch tools require.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoFilter by sender (substring match against the full sender string, i.e. display name + address — not an exact address match)
limitNoMaximum number of results (default: 50, max: 500)
queryNoText to search for in subject, sender, or content
dateToNoEnd date filter (e.g., 'March 1, 2026')
isReadNoFilter by read status
accountNoAccount to search in (omit to search all accounts)
mailboxNoMailbox to search in (e.g., 'INBOX'). Omit to search all mailboxes.
subjectNoFilter by subject line (substring match)
dateFromNoStart date filter (e.g., 'January 1, 2026')
isFlaggedNoFilter by flagged status

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
partialNo
messagesNo
failedMailboxesNo
timedOutAccountsNo
notSearchedMailboxesNo
skippedLargeMailboxesNo
Install Server

TDQS

A4.3/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden for behavioral disclosure. It does disclose return contents and partial-coverage diagnostics, but it does not explicitly state that the operation is read-only or describe any side effects, permissions, or failure behavior. For a search operation the lack of side-effect warnings is less critical, but without annotations the description could still be more explicit.

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 tightly structured with labeled sections: use when, returns, do not use when, and preference guidance. Every sentence serves a functional purpose, and the most actionable guidance is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers what results look like, including diagnostic caveats, explicitly routes the agent away from inappropriate uses, and points to the dependent operations. With an output schema present and all parameters fully documented, nothing essential is missing for an agent to invoke this tool correctly.

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 100%, so the schema already documents all 10 parameters. The description adds a high-level summary of filter categories but no additional semantic detail beyond what the schema provides, so a baseline of 3 is appropriate.

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 action ('finding messages by query/sender/subject/date/read/flag filters') and clearly identifies the resource and the follow-up purpose (obtaining ids). It differentiates itself from list-messages, get-message, and get-thread, so an agent can tell it apart from its siblings.

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?

Explicit 'Use when' and 'Do not use when' sections name the alternative tools (list-messages, get-message, get-thread) and the conditions that make them preferable. It also instructs the agent to prefer this tool first to obtain ids required by other operations, leaving no ambiguity about when to select it.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sweetrb/apple-mail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server