Skip to main content
Glama
yu2001-s
by yu2001-s

create-draft

Create a new email draft in Apple Mail for review before sending. Specify recipients, subject, body, and optional attachments; the draft is saved unsent.

Instructions

Use when: composing an email the user should review in Mail.app before sending — the safe default for any new message. Select a concrete From alias with from after list-sending-identities; account remains as a backwards-compatible account/identity selector. Returns: the stable draft_id, actual From identity, recipients, subject, and attachment count. Do not use when: editing an existing draft (use update-draft) or the user wants it sent now (use send-email). Safety: creates and saves a draft only; it sends nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipients
toYes
bccNoBCC recipients
bodyYes
fromNoSending identity id, email address, or formatted sender from list-sending-identities
accountNoDeprecated compatibility selector: Mail account name or sender address
subjectYes
attachmentsNoFiles to attach: absolute paths (e.g. '/Users/me/report.pdf') and/or inline {filename, contentBase64} objects up to 25 MiB decoded each.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
fromNo
subjectNo
draft_idNo
recipientsNo
attachmentCountNo
Behavior5/5

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

With no annotations, the description explicitly states that the tool only creates and saves a draft and sends nothing, and lists the return values, providing full behavioral clarity. 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.

Conciseness5/5

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

The description is structured, concise, and front-loaded with the primary usage condition. Every section serves a distinct purpose: usage, parameter guidance, return details, exclusion conditions, and safety note. No wasted words.

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?

The description covers purpose, usage conditions, parameter guidance for non-obvious ones, return summary, and safety assurance. Given that the output schema is available (and the description lists key return fields), and the input schema provides details, the description is sufficiently complete for an agent to decide and use the tool correctly.

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 description adds value by explaining the intended use of `from` (alias selection after list-sending-identities) and marking `account` as deprecated, which goes beyond the schema. For other parameters, the schema descriptions (63% coverage) already provide basic info, and the return description hints at their role. This combination effectively compensates for the schema gaps.

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: composing an email for user review before sending, positioning it as the safe default for new messages. It distinguishes it from related actions (editing drafts, sending immediately) and provides usage guidance.

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 usage conditions (when to use and when not to use with specific alternative tool names), and advises on how to select a From alias, making it easy for an agent to decide.

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/yu2001-s/apple-mail'

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