Reply to a message
send_replyReplies to an existing Proton Mail message and sends it in the same conversation, with a confirmation prompt before sending.
Instructions
Replies to a message and sends the reply, with the reference headers that put it in the same conversation. Unlike a reply written as a draft, this one keeps those headers: Proton rewrites them for anything it stores, and this is never stored before it goes. By default every send asks the user to confirm first, through the client, showing the sender, every recipient separated into To, Cc and Bcc, and the subject. It carries no part of the message itself and links to a page where the whole thing can be read as the recipient will see it, and a client that cannot show the question cannot send. The user can allow a tool to send without asking, within bounds they choose; the answer then says that it did. The body is plain text and markup is not interpreted. HTML written here is delivered as visible characters, so the recipient would read the tags rather than see formatting. Give a message its shape with line breaks, blank lines, indentation and plain lists, and write a link as the bare address so that what is read is what is followed. A message may instead be written as markup, in the html field, which is delivered as formatting rather than as visible tags. Give one or the other, not both: a message that carries markup has its plain text half dropped, so the half that was confirmed would never arrive. Permitted are headings, paragraphs, line breaks, rules, quotes, emphasis, lists, tables, links and images, with colour, font, alignment, spacing and borders. Anything else is refused rather than quietly removed, and the answer names what and why. Note that the preview page linked from the confirmation lists every address in the message in full, including the ones behind links and images, and every alt text, because those are what a recipient reads. The question in the client stays short and carries counts instead. Text is UTF-8 everywhere: subject, body and addresses. Write characters as the language actually spells them, including umlauts, accents, sharp s, quotation marks and any other non-ASCII character. Do not transliterate them away (no "ae" for "ä", no "ss" for "ß"): the subject is encoded for transport and decoded again on arrival, and the body carries its character set, both verified against the Bridge. A transliterated message is simply a message with the wrong words in it.
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": {
"messageId": "<messageId>",
"text": "<text>"
},
"name": "send_reply"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | No | Your part of the message as markup instead of plain text. The original is quoted below it either way. The quote keeps the original's own markup, character for character, minus what would reach out of it: style blocks, document-level elements, scripts and comments. A message this server would not itself compose can therefore still be replied to or forwarded, but its formatting travels along, and so does anything a link in it points at. | |
| text | Yes | The reply. The original is quoted below it. | |
| mailbox | No | The mailbox the original is in, if known. | |
| replyAll | No | When true, the other recipients of the original are put in copy. | |
| messageId | Yes | The message being replied to. | |
| markupLevel | No | How much markup is permitted. "standard" covers ordinary formatted mail. "extended" permits every CSS property, including ones that can hide content, and makes the confirmation carry a warning telling the person to open the preview. Prefer "standard"; reach for "extended" only when asked for something that needs it, such as a button, which requires display:inline-block. | standard |