Skip to main content
Glama
sethbang

proton-mail-mcp

reply_email

Reply to an email by reading the original message and sending a reply with correct threading headers (In-Reply-To, References).

Instructions

Reply to an email message. Reads the original message and sends a reply with proper threading headers (In-Reply-To, References). Response leads with a [sent-copy:verified|unverified] token; the [reply-to:*] family of tokens does NOT apply here because this tool doesn't accept a replyTo parameter — there's no requested Reply-To to verify against. If you need Reply-To control or rewriting detection, use send_email. Note: for reply-to-all behavior, prefer the dedicated reply_all_email tool over passing replyAll: true here — both work, but the dedicated tool is more discoverable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesUID of the message to reply to
folderNoFolder containing the original message (default: INBOX)INBOX
bodyNoReply body content (text or HTML). Required unless `markdownBody`.
isHtmlNoWhether the body contains HTML content
markdownBodyNoMarkdown source for the reply — mutually exclusive with `body`/`isHtml`.
sanitizeHtmlNoRun the HTML body through a conservative allowlist (strips scripts, event handlers, inline styles, remote `<img>` beacons). **Defaults to true as of v1.0.0**; pass `false` to preserve full-fidelity HTML. No-op on plain-text bodies.
ccNoAdditional CC recipients, separated by commas
bccNoBCC recipients, separated by commas
replyAllNoReply to all recipients (sender + TO + CC) instead of just sender
includeQuoteNoInclude quoted original message below reply body (default: true)
dryRunNoIf true, resolve the reply recipients (and reply-all fan-out) + subject WITHOUT sending — returns a preview so you can confirm who would receive the reply before it goes out.
Behavior5/5

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

Describes the response token format, threading headers, and the effect of the dryRun parameter. Annotations are non-contradictory, and the description adds significant behavioral context beyond annotations, such as token behavior and dryRun preview.

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?

Three short, front-loaded sentences with no redundancy. Every sentence adds essential information: purpose, token behavior, and usage alternatives.

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 the 11 parameters and no output schema, the description covers main behavior, token, and alternatives. It could mention default behaviors like quoting or auto-marking read, but the core information is sufficient for an email reply tool.

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?

Input schema covers all parameters (100% coverage), so baseline is 3. The description adds value by explaining the dryRun parameter's preview effect and advising against replyAll in favor of the dedicated tool, which is helpful but not extensive.

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 'Reply to an email message' with details about threading headers, clearly differentiating from siblings like send_email and reply_all_email. The verb and resource are specific and 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?

Provides explicit guidance on when to use alternative tools (send_email for Reply-To control, reply_all_email for reply-to-all), and clarifies that the [reply-to:*] tokens do not apply. This is exemplary usage context.

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