Skip to main content
Glama
isityael

Apple Mail MCP Server

by isityael

mark_emails

Batch update email status: mark as read, unread, flagged, or unflagged. Filter by subject, sender, mailbox, or age to organize your inbox efficiently.

Instructions

Batch mark emails as read/unread and/or flagged/unflagged.

At least one filter (subject_keyword, sender, or older_than_days) is required.

Args: account: Account name (e.g., "Gmail", "Work") action: Action to perform: "read", "unread", "flagged", "unflagged" subject_keyword: Optional keyword to filter emails by subject sender: Optional sender email/name to filter by mailbox: Mailbox to search in (default: "INBOX") older_than_days: Only affect emails older than N days max_emails: Maximum number of emails to update (safety limit, default: 50)

Returns: Summary of affected emails

User Preferences: {"workflow": "default", "notifications": "enabled"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
senderNo
accountYes
mailboxNoINBOX
max_emailsNo
older_than_daysNo
subject_keywordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses safety limit (max_emails) and required filters, but does not mention idempotency, error handling, or behavior when no emails match.

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?

Efficiently structured with a one-line summary, a requirement statement, and a clear Args list. No redundant or extra sentences.

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?

Covers key aspects: operation, required filters, all parameters with explanations, safety limit, and return summary. Lacks details on output schema and error scenarios, but adequate given no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the Args section adds meaning: it clarifies filters are optional, explains max_emails as safety limit, and describes each parameter's role. Compensates well for missing schema descriptions.

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?

Description states 'Batch mark emails as read/unread and/or flagged/unflagged' with a specific verb and resource. It clearly distinguishes from siblings like update_email_status (single email) by emphasizing batch operation and required filters.

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

Usage Guidelines4/5

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

Indicates at least one filter required and lists filter parameters, implying multi-condition batch use. However, no explicit comparison to sibling tools or when-not-to-use.

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/isityael/apple-mail-mcp'

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