Apple Mail

by yu2001-s

Overview Schema Source Related Servers Discussions Admin

create-newsletter-smart-mailboxes

Auto-discover newsletter and bulk senders in your inboxes, then propose or create a dedicated smart mailbox per sender. Start with a dry run to review before making changes.

Instructions

Use when: auto-discovering newsletter/bulk senders in your INBOX(es) and (optionally) creating a dedicated smart mailbox per sender (named "NL: "). Defaults to a safe dry run that only proposes. Returns: the proposed or created smart mailboxes with their match scores. Do not use when: you already know the exact sender (use create-smart-mailbox) or want real folders (use create-mailbox). Safety: with dryRun=false it edits Apple Mail's SyncedSmartMailboxes.plist (backed up, atomic, existing entries preserved) and can create many smart mailboxes at once — review a dryRun first. It scans up to ~400 recent messages per inbox via AppleScript, which can be slow on large mailboxes.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Look back this many days in INBOXes
`dryRun`	No	If true (default), only propose; if false, actually create
`minCount`	No	Minimum messages from sender in the period

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`dryRun`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations provided, so the description fully carries the burden. It discloses that with dryRun=false the tool edits SyncedSmartMailboxes.plist (with backup and atomic preservation), can create many smart mailboxes at once, scans up to ~400 recent messages per inbox via AppleScript, and notes performance impact on large mailboxes. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (use when, returns, do not use when, safety). It is slightly verbose but every sentence adds value. No redundancy with schema or annotations.

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 tool's complexity (auto-discovery, smart mailbox creation, dry run, plist editing), the description covers purpose, usage, behavior, safety, and performance. An output schema exists, so return values are documented. The description is comprehensive and sufficient for an AI agent to correctly select and invoke the tool.

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?

The input schema has 100% description coverage for all three parameters (days, dryRun, minCount). The description adds extra context beyond the schema, such as the scanning limit (~400 messages) relating to the days parameter, and the safety of dryRun. While the schema is good, the description enhances understanding.

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 explicitly states the tool's purpose: auto-discovering newsletter/bulk senders and optionally creating smart mailboxes per sender. It clearly distinguishes from siblings like create-smart-mailbox and create-mailbox by specifying contexts where those alternatives should be used.

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?

The description provides explicit 'Use when' and 'Do not use when' sections with specific alternatives. It also advises to default to dry run and review proposals before executing, giving clear usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server