Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

list-messages

List recent mailbox messages with sender/unread filters and pagination to get IDs for read, mark, delete, or move operations.

Instructions

Use when: browsing a mailbox's recent messages (optionally filtered by sender or unread-only) with pagination via limit/offset, and you need their ids. Returns: messages with id, date, subject, and sender (plus partial-coverage diagnostics when some mailboxes were skipped). Do not use when: you have specific search criteria like subject/date/flags (use search-messages) or already have an id and want the body (use get-message). Like search-messages, use this to obtain the ids that read/mark/delete/move and batch tools require.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoFilter by sender email address or name
limitNoMaximum number of messages (default: 50, max: 500)
offsetNoNumber of messages to skip (for pagination)
accountNoAccount to list messages from
mailboxNoMailbox to list messages from. Omit to list from all mailboxes.
unreadOnlyNoOnly show unread messages

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?

With no annotations, the description carries the burden of behavioral disclosure. It explains the return fields (id, date, subject, sender) and the partial-coverage diagnostics, which goes beyond a generic list description. However, it does not mention ordering, default account behavior, or pagination semantics beyond limit/offset, leaving minor gaps.

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 structured with a front-loaded 'Use when,' followed by return details and 'Do not use when,' all in three concise sentences. Every sentence conveys essential guidance without fluff or repetition.

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 6-parameter input schema and the existence of an output schema, the description provides sufficient context: usage scenarios, exclusions, return value summary, and diagnostic behavior. The mention of related batch tools completes the operational picture for an AI agent.

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% with clear parameter descriptions, so the baseline is 3. The description adds contextual framing (e.g., 'unread-only' and 'pagination'), but does not introduce meaning that the schema already provides. It appropriately avoids redundancy.

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 clearly states the tool lists a mailbox's recent messages with optional filters and pagination to obtain IDs. It explicitly distinguishes from search-messages (specific criteria) and get-message (fetching body by ID), making the purpose unambiguous among 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?

Provides explicit 'Use when' and 'Do not use when' guidance, naming alternatives such as search-messages and get-message, and clarifies the tool's role in supplying IDs for mutation/batch tools. This is comprehensive and actionable.

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