Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25

edit_draft

Update an existing email draft by modifying specific fields such as recipients, subject, or body. The system atomically replaces the draft while preserving any unchanged fields from the original.

Instructions

Edit an existing draft email. Since JMAP emails are immutable, this atomically destroys the old draft and creates a new one with the updated fields. Only fields you provide will be changed; others are preserved from the original draft.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoUpdated CC email addresses (optional)
toNoUpdated recipient email addresses (optional, keeps existing if omitted)
bccNoUpdated BCC email addresses (optional)
fromNoUpdated sender email address (optional)
emailIdYesThe ID of the draft email to edit
replyToNoReply-To email addresses (replies go here instead of to the sender)
subjectNoUpdated email subject (optional)
htmlBodyNoUpdated HTML body (optional)
textBodyNoUpdated plain text body (optional)
Behavior5/5

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

The description discloses critical behavioral traits: it atomically destroys the old draft and creates a new one, and fields not provided are preserved. Since no annotations exist, the description fully carries the burden of transparency, and does so effectively.

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 two sentences: first states the purpose, second adds crucial behavioral detail. No extraneous information; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the task and behavioral nuances well, but it omits any mention of the return value (e.g., the new draft ID or object). Since there is no output schema, this information would aid completeness for an agent.

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?

All 9 parameters have descriptions in the input schema (100% coverage). The description adds value by explaining the merge behavior: 'Only fields you provide will be changed; others are preserved from the original draft.' This clarifies how optional parameters interact.

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 clearly states the tool edits an existing draft email, specifying the verb 'edit' and the resource 'draft email'. It distinguishes from siblings like 'create_draft' by noting immutability and atomic destroy+create behavior.

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

Usage Guidelines3/5

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

The description implies usage context by explaining that only provided fields change and others are preserved. However, it does not explicitly state when to use this tool vs alternatives like 'create_draft' or 'send_draft', nor mention any prerequisites or exclusions.

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/MadLlama25/fastmail-mcp'

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