Skip to main content
Glama
TG-Techie

apple-mail-mcp

by TG-Techie

create_rule

Create a new Apple Mail rule by specifying conditions and actions like move, copy, mark, delete, or forward. Supports match logic and enabled state.

Instructions

Create a new Mail.app rule.

Additive — no confirmation prompt. Mail.app appends new rules to the end of the rule list, so the returned rule_index equals the new total rule count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRule display name. Need not be unique.
actionsYesDict with at least one truthy entry from: - move_to: {"account": str, "mailbox": str} - copy_to: {"account": str, "mailbox": str} - mark_read: bool - mark_flagged: bool (with optional flag_color enum) - flag_color: 'none' | 'red' | 'orange' | 'yellow' | 'green' | 'blue' | 'purple' | 'gray' - delete: bool - forward_to: list[str] of email addresses
enabledNoWhether the rule is enabled on creation. Default True.
conditionsYesList of condition dicts (at least one required). Each: - field: 'from' | 'to' | 'subject' | 'body' | 'any_recipient' | 'header_name' - operator: 'contains' | 'does_not_contain' | 'begins_with' | 'ends_with' | 'equals' - value: substring or value to match - header_name: required iff field == 'header_name'
match_logicNo'all' (AND across conditions) or 'any' (OR). Default 'all'.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: 'Additive — no confirmation prompt' and that it appends to the end of the rule list, explaining that the returned rule_index equals the new total count. This goes beyond what a schema would naturally imply, though it omits details like idempotency or error behavior, so a 4 is appropriate.

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?

Two sentences, zero filler. The purpose is front-loaded, and the behavioral note is efficient and directly relevant. Every word earns its place, making it highly scannable for an agent.

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?

The description covers the essential behavioral context (additive, append, return semantics) and the schema handles parameter details. Given the tool's moderate complexity (nested objects, output schema), it's complete enough for an agent to call it correctly. An explicit mention of prerequisites or side effects would make it a 5, but this is solid.

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%, meaning every parameter is already documented with types, defaults, and formats in the input schema. The description adds no additional parameter-level detail, so the baseline score of 3 is correct — the schema does the heavy lifting.

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 opens with 'Create a new Mail.app rule' — a specific verb and resource. It clearly identifies the tool's action and object, and the term 'new' distinguishes it from update/delete operations. There is no ambiguity about what this tool does.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this tool versus alternatives like update_rule or list_rules. It implies usage for creating rules but never says 'use this when you need a new rule' or contrasts with sibling tools. The only usage-related guidance is 'Additive,' which is more behavioral than contextual.

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

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