Multi Mail

Draft a reply

drafts_reply

Compose a reply to a message as a draft, inside the thread it answers and quoting it below the reply: to whoever wrote it, or with replyAll to everyone on it. Nothing leaves the mailbox until the draft is sent.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	Who to copy, instead of those replyAll copies.
`to`	No	Who the reply goes to, instead of whoever wrote the message and, with replyAll, those it was sent to.
`bcc`	No	Who to blind-copy. The other recipients are not told.
`body`	Yes	The reply text.
`html`	No	The message as HTML, for formatting; body stays its plain-text version. An Outlook mailbox keeps only the HTML and writes the plain version from it.
`mailbox`	Yes	The mailbox's name or its email address.
`replyAll`	No	Also address everyone the message was sent to and copied - never its blind copies, never this mailbox.
`messageId`	Yes	The provider's own identifier.
`attachments`	No	Files to carry: one held by a connected mailbox of the draft's own provider, or content you write out.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`link`	No
`threadId`	No
`previousVersionId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026
- addedOutput schema / properties / previousVersionId
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "id",
-  "link"
-]New value: +[
+  "id"
+]
```

Changed2 schema fields changedOct 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / bcc / items / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / cc / items / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / to / items / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only state readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds real behavioral context beyond that: the draft is created inside the source thread, the original is quoted beneath the reply, and no mail is dispatched by this call. It doesn't cover provider/permission constraints, but the added context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the purpose before the addressing modes and the no-send safety note. No filler, though the middle clause about quoting is slightly dense.

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?

An output schema exists, so return values need no explanation, and the 9 parameters are fully described in the schema. The description covers the essential draft semantics; only provider/permission prerequisites for the underlying message are left implicit.

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?

Schema description coverage is 100%, so every parameter (including replyAll, to, cc, bcc, html, attachments) is already documented in the schema. The description reinforces replyAll's meaning ("to whoever wrote it, or with replyAll to everyone on it") but adds no new syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: compose a reply as a draft, and it states the key structural facts (inside the thread it answers, quoting the original below). It does not explicitly differentiate itself from siblings like messages_reply or drafts_create, so it falls short of a 5.

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

Usage Guidelines3/5

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

"Nothing leaves the mailbox until the draft is sent" implies the when-to-use case (draft-first vs. immediate send) but never names or rules out an alternative such as messages_reply or drafts_send. Usage is inferable but not explicit.

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

All Multi Mail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.