Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

list-messages

Retrieve a paginated list of messages from a mailbox, filtered by sender or unread status. Get IDs, dates, subjects, and senders for further actions.

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 full burden. It discloses return fields (id, date, subject, sender) and mentions partial-coverage diagnostics when some mailboxes are skipped. It doesn't specify ordering or rate limits, but for a read-only list tool, the main behaviors are covered.

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 concise (5-6 lines) and well-structured with clear sections (Use when, Returns, Do not use when). Front-loaded with purpose and no redundant sentences.

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 output schema exists, the description still adds value by detailing return fields and partial-coverage edge cases. It places the tool in the ecosystem (IDs needed for batch tools) and covers filtering and pagination thoroughly.

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 baseline is 3. The description notes optional filters and pagination but adds no new details beyond what the schema already provides for each parameter.

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 starts with 'Use when: browsing a mailbox's recent messages...' which clearly identifies the verb (list), resource (messages), scope (recent, filtered, paginated), and output (ids). It also explicitly contrasts with sibling tools like search-messages and get-message, distinguishing the tool's purpose.

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?

Contains explicit 'Use when:' and 'Do not use when:' sections that specify conditions (browsing recent messages, optional filters, pagination) and name alternatives (search-messages for specific criteria, get-message for body). Also advises on obtaining IDs for batch operations, providing workflow context.

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