Skip to main content
Glama
sethbang

proton-mail-mcp

save_draft

Save an email as a draft without sending it, stored in the Drafts folder. Optionally replace an existing draft atomically to avoid losing the original.

Instructions

Save an email as a draft without sending it. The draft is placed in the user's \Drafts special-use folder (resolved at runtime; falls back to literal Drafts if no annotation). The destination is intentionally not caller-controlled — prior versions accepted an arbitrary folder parameter that allowed planting \Draft-flagged messages in INBOX or other paths, which was confusing to anyone scanning the mailbox.

Pass replaceDraftUid to atomically replace a previous draft instead of appending a new one — the new draft is APPENDed first, then (only on success) the old one is deleted, so a failed append leaves your original draft intact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient email address(es), comma-separated
subjectYesEmail subject line
bodyNoEmail body content (plain text or HTML). Required unless `markdownBody` is provided.
isHtmlNoWhether `body` contains HTML content
markdownBodyNoMarkdown source — rendered to HTML before saving. Mutually exclusive with `body`/`isHtml`.
sanitizeHtmlNoRun the HTML body through a conservative allowlist (strips scripts, event handlers, inline styles, remote `<img>` beacons) before APPEND. Default `true` for safer-by-default drafts. No-op on plain-text.
ccNoCC recipient(s), comma-separated
bccNoBCC recipient(s), comma-separated
replyToNoReply-To email address. Note: Proton SMTP may rewrite or ignore values that don't match authenticated identities.
fromNameNoDisplay name for the From field. Rejects values containing `@` by default to prevent display-name-as-address spoofing — pass `allowAddressLikeFromName: true` to override.
allowAddressLikeFromNameNoOpt-in escape valve for `fromName` containing `@`. Default false.
replaceDraftUidNoOptional UID of a previous draft in the Drafts folder to atomically replace. The new draft is APPENDed first; the old one is deleted only after the append succeeds, so a failed append never destroys the original. Errors if the UID doesn't exist in Drafts.
Behavior4/5

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) are all false. The description adds significant context: atomic replace with replaceDraftUid (APPEND-then-delete), folder fallback behavior, and that the folder is immutable. No contradiction with annotations.

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?

Two well-structured paragraphs with front-loaded purpose. Every sentence provides necessary detail. No redundancy or fluff. The historical note is concise.

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 12 parameters and no output schema, the description covers key behavior: draft location, immutable folder, atomic replacement, and parameter interactions (mutual exclusivity of body/markdownBody, sanitization defaults). It is complete for agent decision-making.

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%, so baseline is 3. The description adds value beyond schema by explaining the atomic replace workflow for replaceDraftUid and the rationale for missing folder parameter. This 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 clearly states 'Save an email as a draft without sending it', which is a specific verb+resource combination. It distinguishes from sibling tools like send_email by emphasizing the draft nature and lack of delivery.

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

Usage Guidelines4/5

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

The description explains when to use (save draft) and provides context on the fixed Drafts folder destination, preventing misuse. It lacks explicit comparison to alternatives but implies usage via behavioral details.

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/sethbang/proton-mail-mcp'

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