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
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UID of the message to reply to | |
| folder | No | Folder containing the original message (default: INBOX) | INBOX |
| body | No | Reply body content (text or HTML). Required unless `markdownBody`. | |
| isHtml | No | Whether the body contains HTML content | |
| markdownBody | No | Markdown source for the reply — mutually exclusive with `body`/`isHtml`. | |
| sanitizeHtml | No | Run 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. | |
| cc | No | Additional CC recipients, separated by commas | |
| bcc | No | BCC recipients, separated by commas | |
| replyAll | No | Reply to all recipients (sender + TO + CC) instead of just sender | |
| includeQuote | No | Include quoted original message below reply body (default: true) | |
| dryRun | No | If 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. |