Skip to main content
Glama
gmail-mcp
by gchallen

reply

Send a threaded Gmail response to a message, using the sender and original To/Cc recipients by default, or save it as a draft for review before sending.

Instructions

Reply to a message with Gmail's default recipients: the sender (or Reply-To), plus everyone on To and Cc except yourself when replyAll is true. Threaded, subject prefixed with Re:, original quoted below, signature appended. Sends immediately unless asDraft is true, which leaves a draft to review. to/cc/bcc override the defaults.

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>"
    },
    "name": "reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoOverride the default Cc.
toNoOverride the default To.
bccNo
bodyNoPlain-text body. One line per paragraph, no hard wrapping; Gmail wraps on display and links bare URLs. Markdown does NOT render: for bullets or other formatting supply htmlBody instead.
quoteNoDefault true.
asDraftNoCreate a draft instead of sending. Default false.
htmlBodyNoHTML body, used when the message needs formatting such as <ul><li> lists. When given, "body" becomes the plain-text alternative (derived from the HTML if omitted). Do not include the signature; it is appended.
replyAllNoDefault false.
messageIdYesThe message to reply to; usually the latest in the thread (see get_thread).
signatureNoSet false to send without the configured signature. By default the signature (from config.json, GMAIL_SIGNATURE, or the Gmail settings signature) is appended once; a copy typed into the body is de-duplicated.
attachmentsNoFiles to attach, as local paths (preferred: any size up to Gmail's 25 MB total) or base64 objects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the write/open-world/non-destructive profile; the description adds genuinely new behavior — sends immediately by default, threading and Re: subject mutation, quote-below and signature append with de-duplication. It omits failure modes and what a successful call returns, which for a send-side mutation would be useful.

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?

Four dense sentences, front-loaded with recipient derivation, then side effects, then the send-vs-draft switch, then override escape hatch. No filler and no restatement of field names already documented in the schema.

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 mutation with no output schema, it covers the consequential defaults (replyAll, asDraft, signature, quote, override behavior). It does not describe the result of the call or error conditions, which would round out a send-side tool with no output schema to lean on.

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?

Schema coverage is 91% so the baseline is 3, but the description earns above it by explaining the default-recipient composition (sender or Reply-To, plus To/Cc excluding yourself) and the override relationship of to/cc/bcc — semantics the per-field descriptions don't convey. Remaining params such as quote and signature are only lightly touched.

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?

Opens with a specific verb+resource ("Reply to a message") and immediately distinguishes itself from plain send/create_draft by describing Gmail's reply-specific recipient derivation rules. An agent can tell this is the threaded reply path, not forward or send_message.

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 clear conditions for the two modes that matter: replyAll expands to To/Cc minus yourself, asDraft leaves a draft to review, and to/cc/bcc override defaults. It stops short of naming siblings like forward or send_message as alternatives, so the choice between reply-in-thread and a fresh send is left implicit.

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