Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

create-rule

Create an Apple Mail rule to automatically manage incoming messages: set conditions on sender, subject, or content, then choose actions like mark as read, flag, delete, or move to a folder.

Instructions

Use when: creating a new Mail rule with one or more conditions (field/operator/value) and at least one action (markRead, markFlagged, delete, or moveTo). Set matchAll to require all conditions vs. any. Returns: a confirmation naming the rule and its condition count. Do not use when: toggling an existing rule (use enable-rule / disable-rule) or removing one (use delete-rule). Use list-rules to avoid duplicating an existing rule. Safety: creates a rule that automatically acts on real mail (including delete/move actions) on an ongoing basis — confirm the conditions and actions with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
actionsYes
enabledNoEnable immediately; defaults to false so the rule must be reviewed first
matchAllNo
conditionsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
createdNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Despite no annotations, the description discloses that creating a rule has ongoing safety implications, including automatic action on real mail and the need to confirm with the user. It also mentions the default enabled state from the schema, adding behavioral context beyond the schema.

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 well-organized with 'Use when', 'Returns', 'Do not use when', and 'Safety' sections, each adding unique value. It is concise yet comprehensive, with minimal fluff.

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 complex nested schema and no annotations, the description covers safety, usage boundaries, and return format, making it complete for an agent to use without additional external context.

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 coverage is low (20%) and the description explains key fields like matchAll, actions, and conditions, and references the enabled default. It could detail sub-fields (e.g., operators) but the core parameters are clarified.

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 the tool creates a new Mail rule, with specifics on conditions and actions. It is clearly distinct from siblings like enable-rule and delete-rule. The purpose is explicit and actionable.

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' scenarios, naming alternative tools (enable-rule, disable-rule, delete-rule, list-rules). This directly guides the agent on when to invoke this tool versus siblings, which is exemplary.

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