Skip to main content
Glama

Send Email Reply to All

send_reply_all
Destructive

Send an immediate reply to all email recipients, threaded into the conversation with the original message quoted. Use create_reply_all_draft to review before sending.

Instructions

Reply to all recipients of an email and send immediately. Threads into the conversation and quotes the original. Use create_reply_all_draft to review before sending.

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": {
      "message_id": "<message_id>",
      "comment": "<comment>"
    },
    "name": "send_reply_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesReply content (added above the quoted original)
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
message_idYesThe message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond them: the send is immediate, the message threads into the existing conversation, and the original is quoted. It does not mention permission requirements or whether the sent copy is retrievable, but the irreversibility implication is clear.

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?

Three short sentences, front-loaded with the action and its immediacy, then the threading behavior, then the alternative. No wasted wording.

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 a three-parameter mutation tool with no output schema, the description covers what happens (send now, thread, quote) and the safer alternative. Minor gaps remain around failure modes and permissions, but nothing essential to correct invocation 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 100%, so message_id, comment, and mailbox are already documented, including the delegated-mailbox constraint. The description adds only the note that the reply is placed above the quoted original, which is largely redundant with the schema's comment description. 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 and resource ('Reply to all recipients of an email') plus the immediate-send behavior, which distinguishes it from send_reply (single recipient) and from the draft variant. An agent can identify the operation without opening the 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?

Explicitly names the alternative 'create_reply_all_draft' and the condition that selects it ('to review before sending'). It does not spell out when-not to use this tool beyond that, but the send-now vs. draft-first split is the key decision and it is covered.

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

Deploy Server

Other Tools