Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_reply

Reply to an existing email within its thread, optionally to all original recipients or custom To/Cc/Bcc. Add attachments, a signature, or extra recipients across Gmail, Outlook, iCloud, and IMAP.

Instructions

Reply to an existing email, in its thread. With replyAll the reply goes to the original sender and all To and Cc recipients, except the account's own address

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": {
      "accountId": "<accountId>",
      "emailId": "<emailId>",
      "body": "<body>"
    },
    "name": "email_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCc recipients. Replaces any Cc carried over by replyAll
toNoReplace the default To (the original sender). Use it when the original was sent by you, so the reply goes to the real correspondents instead of back to yourself
bccNo
bodyYes
emailIdYes
replyAllNo
accountIdYes
signatureNoAdd the account's signature (default true). Gmail: the signature of the send-as address the mail goes out from, read from Gmail's settings, in Gmail's own markup above any quoted history; a body that already holds one is left alone. Outlook.com, iCloud and IMAP have no signature a client can read, so nothing is added there. The result's `signature` field says what happened
attachmentsNoFiles to attach, at most 100. Total size is capped at 25 MB
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)
additionalRecipientsNoExtra To recipients added to the default or given To (deduplicated by address)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses thread placement and how replyAll resolves recipients while excluding the account's own address, but it is silent on the fact that this sends mail irreversibly, how the sent copy is stored, and what happens with the signature default (that detail lives only in the schema).

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 sentences, no filler, and the core identity of the tool is front-loaded before the replyAll nuance. Nothing would be lost by keeping it exactly as is.

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 send operation with no annotations and no output schema, the description covers the key ambiguous behavior (recipient resolution) and the rich schema covers most of the rest. It could say more about send-side effects, but nothing essential to invoking it correctly is missing.

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 55%, so the baseline is 3. The description does add real meaning for replyAll, the one parameter it discusses, by spelling out recipient resolution and self-address exclusion; the other undocumented parameters (emailId, accountId, body, bcc) get no help from the description.

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?

States a specific verb and resource ('Reply to an existing email') plus a scope detail ('in its thread'), which separates it from forward and draft creation without naming them. It stops short of explicit sibling differentiation, so it is clear but not maximal.

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?

The second sentence explains the replyAll recipient resolution, which is behavioral guidance rather than when-to-use guidance. There is no statement about when to choose this over email_forward or email_draft_create, and no exclusions or prerequisites.

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