Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

search-messages

Search emails by query, sender, subject, date, read status, or flags. Returns message IDs for follow-up operations like reading, marking, or deleting.

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
timedOutAccountsNo
notSearchedMailboxesNo
skippedLargeMailboxesNo
Behavior4/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 discloses return fields (id, date, subject, sender, read state) and mentions partial-coverage diagnostics. While it doesn't explicitly state the tool is read-only, 'search' implies non-destructive behavior, and the description adds meaningful context about response structure.

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?

Three sentences, each serving a distinct purpose: usage trigger, return description, and exclusions. No wasted words, and the most critical information appears first. Highly efficient.

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?

Given the tool's complexity (10 parameters, no annotations) and presence of an output schema, the description covers when to use, what it returns, and explicit exclusions. It is comprehensive for a search tool without needing reference to annotations.

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% with detailed parameter descriptions (e.g., 'substring match' for from/subject). The description does not add significant additional meaning beyond the schema, as it only reiterates that filters are available. Baseline 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 explicitly states 'Use when: finding messages by query/sender/subject/date/read/flag filters' with a specific verb and resource. It distinguishes from sibling tools like list-messages, get-message, and get-thread, making the tool's purpose extremely clear.

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?

The description provides explicit 'Use when:' and 'Do not use when:' instructions, listing alternative tools for different scenarios (e.g., list-messages for plain listing, get-message for body retrieval). This gives clear context and exclusions.

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

Install Server

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