Email MCP Server

Overview Schema Source Related Servers Discussions Admin

save_draft

Save email drafts to the Drafts folder for later editing and sending. Compose at your own pace, then use send_draft to deliver when ready.

Instructions

Save an email draft to the Drafts folder. Compose over time, then use send_draft to send it. Use list_emails with the Drafts mailbox to see saved drafts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "save_draft"
  }
}

Input Schema

Name	Required	Description
`cc`	No	CC recipients
`to`	No	Recipient email addresses (can be empty for drafts)
`bcc`	No	BCC recipients
`body`	Yes	Email body content
`html`	No	Send as HTML (default: plain text)
`account`	Yes	Account name from list_accounts
`subject`	Yes	Email subject
`in_reply_to`	No	Message-ID for threading (from get_email)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Aug 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the tool as non-readonly and non-destructive, so the bar is lower. The description adds useful lifecycle context—'compose over time' and how drafts are later sent or listed—without contradicting annotations. It doesn't mention side effects like overwriting, but the added workflow detail is valuable.

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 three sentences with a clear front-loaded purpose, followed by workflow and viewing guidance. No filler or redundancy; every sentence contributes to tool understanding.

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?

Given 8 parameters and no output schema, the description provides the essential workflow context (save, send, view drafts) that an agent needs. It doesn't explain return values, but the lifecycle and intent are sufficiently covered for a draft-saving tool.

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?

The input schema has 100% parameter description coverage, so the schema carries the burden. The description doesn't introduce new parameter details, but it implies the draft workflow (e.g., saving without sending), which is consistent with the schema's note that 'to' can be empty for drafts. Baseline 3 is appropriate.

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 states a specific action and resource: 'Save an email draft to the Drafts folder.' It distinguishes from sibling tools by explicitly referencing send_draft for sending and list_emails for viewing drafts, making the purpose unambiguous.

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?

It provides clear when-to-use guidance: 'Compose over time, then use send_draft to send it.' It also names the alternative for viewing drafts ('Use list_emails with the Drafts mailbox'), offering explicit contextual direction beyond just stating the action.

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