Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb

send-serial-email

Send individually personalized emails to multiple recipients using placeholder substitution in subject and body. Each recipient receives a unique copy without seeing others.

Instructions

Use when: the user has confirmed a mail-merge — sending individually personalized copies to many recipients (max 100), with {{Key}} placeholders in subject/body replaced per-recipient from each recipient's variables. Recipients do not see each other. Returns: a per-recipient sent/failed report with counts. Do not use when: sending one message to a shared recipient list (use send-email) or saving for review (use create-draft). Safety: this SENDS many real emails immediately and they cannot be unsent — require explicit user confirmation of the recipient list, the subject/body template, and the placeholder substitutions before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesEmail body — use {{Key}} for placeholders
accountNoAccount to send from
delayMsNoDelay between sends in ms (default: 500, max: 10000)
subjectYesSubject line — use {{Key}} for placeholders
recipientsYesList of recipients with personalization variables (max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
sentNo
failedNo
resultsNo
Behavior5/5

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

Discloses that the tool sends many real emails immediately and irreversibly, and returns a per-recipient sent/failed report. No annotations provided, so description fully handles this.

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?

Front-loaded with decision criteria, followed by behavior, return, exclusions, and safety. Concise and well-organized without redundancy.

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?

Covers all essential aspects: when to use, safety, return format, and parameter behavior. Output schema exists, so lack of detail there is acceptable.

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 100%, but description adds context about placeholder syntax {{Key}}, max recipients 100, delay defaults and limits, and the account parameter's role.

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?

Clearly defines the tool as mail-merge with personalized copies using placeholders. Distinguishes from sibling tools like send-email and create-draft.

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' conditions, referencing alternative tools and requiring user confirmation for safety.

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