mailmcp

Reply as a draft

reply_draft

Saves a reply to a message into Drafts, in the same thread: threading headers, "Re:" subject, recipients (sender, or all with reply_all) and the quoted original are set by the server. Use whenever the owner says "reply / write a draft" ("odpověz", "napiš koncept"). Nothing is sent.

Input Schema

TableJSON Schema

Name	Required	Description
`uid`	Yes	uid being answered
`html`	No	Optional HTML version
`lang`	No	"On … wrote:" language
`text`	No	Plain text; the original is quoted
`vars`	No	Values for its {{placeholders}}
`quote`	No	Quote the original (default true)
`folder`	No	Default: Gmail All Mail, else INBOX
`account`	Yes	list_accounts id
`template`	No	list_templates name (paid)
`reply_all`	No	Reply to all (default: sender only)
`attachments`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 5, 2026

changedInput schema / properties / account / description

Previous value: -"Account id from list_accounts"New value: +"list_accounts id"

changedInput schema / properties / attachments / items / description

Previous value: -"Attach a mailbox attachment {uid, part[, folder, account]}, inline content {filename, content[, encoding]}, or a local file {path}"New value: +"{uid, part[, folder, account]} from a mailbox, {filename, content[, encoding]} or {path}"

removedInput schema / properties / attachments / items / properties / account / description
```
Removed value: -"Account holding the file (defaults to the sending account)"
```

removedInput schema / properties / attachments / items / properties / content / description

Removed value: -"File content, UTF-8 text or base64 (see encoding); for files the assistant writes itself"

removedInput schema / properties / attachments / items / properties / content_type / description
```
Removed value: -"MIME type of inline content, e.g. text/csv"
```
removedInput schema / properties / attachments / items / properties / encoding / description
```
Removed value: -"How `content` is encoded, default utf8"
```
removedInput schema / properties / attachments / items / properties / filename / description
```
Removed value: -"File name (required for inline content)"
```

removedInput schema / properties / attachments / items / properties / folder / description

Removed value: -"Folder of the source message (e.g. \"mailmcp-uploads\" for uploaded files)"

changedInput schema / properties / attachments / items / properties / part / description

Previous value: -"Attachment part id from get_message / list_uploads"New value: +"Part id from get_message / list_uploads"

changedInput schema / properties / attachments / items / properties / path / description

Previous value: -"Local file path (Claude Desktop / Claude Code only, within policy.attachment_dirs)"New value: +"Local path (stdio only, inside policy.attachment_dirs)"

removedInput schema / properties / attachments / items / properties / uid / description
```
Removed value: -"uid of the source message"
```

changedInput schema / properties / folder / description

Previous value: -"Folder/label path. Defaults to All Mail on Gmail, INBOX elsewhere."New value: +"Default: Gmail All Mail, else INBOX"

changedInput schema / properties / html / description

Previous value: -"Optional HTML version of the reply body"New value: +"Optional HTML version"

changedInput schema / properties / lang / description

Previous value: -"Language of the \"On … wrote:\" line (default: guessed from the reply)"New value: +"\"On … wrote:\" language"

changedInput schema / properties / quote / description

Previous value: -"Quote the original under the reply (default true)"New value: +"Quote the original (default true)"

changedInput schema / properties / reply_all / description

Previous value: -"Reply to every recipient of the original (default: sender only)"New value: +"Reply to all (default: sender only)"

addedInput schema / properties / template

Added value: +{
+  "description": "list_templates name (paid)",
+  "maxLength": 60,
+  "type": "string"
+}

changedInput schema / properties / text / description

Previous value: -"The reply itself, plain text, without greeting-to-quote artefacts; the original is quoted automatically"New value: +"Plain text; the original is quoted"

changedInput schema / properties / uid / description

Previous value: -"uid of the message being answered (from search_messages / get_message / get_thread)"New value: +"uid being answered"

addedInput schema / properties / vars

Added value: +{
+  "additionalProperties": {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  "description": "Values for its {{placeholders}}",
+  "propertyNames": {
+    "pattern": "^[a-z_][a-z0-9_]{0,30}$",
+    "type": "string"
+  },
+  "type": "object"
+}

changedInput schema / required

Previous value: -[
-  "account",
-  "uid",
-  "text"
-]New value: +[
+  "account",
+  "uid"
+]

Changed11 schema fields changedSep 22, 2026
- addedInput schema / properties / attachments / items / properties / uid / maxLength
```
Added value: +512
```
- removedInput schema / properties / attachments / items / properties / uid / maximum
```
Removed value: -9007199254740991
```
- addedInput schema / properties / attachments / items / properties / uid / minLength
```
Added value: +1
```
- removedInput schema / properties / attachments / items / properties / uid / minimum
```
Removed value: -1
```
- changedInput schema / properties / attachments / items / properties / uid / type
```
Previous value: -"integer"New value: +"string"
```
- addedInput schema / properties / attachments / maxItems
```
Added value: +20
```
- addedInput schema / properties / uid / maxLength
```
Added value: +512
```
- removedInput schema / properties / uid / maximum
```
Removed value: -9007199254740991
```
- addedInput schema / properties / uid / minLength
```
Added value: +1
```
- removedInput schema / properties / uid / minimum
```
Removed value: -1
```
- changedInput schema / properties / uid / type
```
Previous value: -"integer"New value: +"string"
```
First observedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare write/non-destructive/non-idempotent/open-world, so the bar is lower; the description still adds real value by disclosing that the server auto-populates threading headers, the 'Re:' subject, recipients and the quoted original, and by confirming nothing is sent. It omits what the call returns and whether repeat calls create duplicate drafts.

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 tight sentences, front-loaded with the action and scope; the server-side behavior list and the trigger phrase each earn their place, and there is no filler.

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?

For an 11-parameter tool with nested attachment objects, no output schema and annotations covering safety, the description covers purpose, threading behavior and non-send semantics adequately. Minor gaps remain around the response shape and duplicate-draft behavior on repeat calls.

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 91%, so the schema already documents uid, reply_all, quote, lang, folder and the attachment shapes. The description only restates reply_all and the quoted original, adding no format or syntax detail beyond the structured fields; baseline 3 applies.

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?

States a specific verb (Saves) and resource (a reply to a message into Drafts) with the key differentiator 'in the same thread' and 'Nothing is sent', which separates it from reply_send, send_draft and create_draft without opening any schema.

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?

Gives a clear trigger ('Use whenever the owner says "reply / write a draft"', with localized examples), so an agent knows when to reach for it. It stops short of naming reply_send or create_draft as the alternatives, so the routing is implied by 'Nothing is sent' rather than stated.

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

All mailmcp 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.

Reply as a draft

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources