Skip to main content
Glama

Send a customer email reply

send_customer_email_reply
Destructive

Sends one reply to one customer email, from the store's mailbox, to the address the email came from. Only an email with a ready Emporiqa draft can be answered; text replaces the draft's words when given. The reply is billed like a drafted reply sent from the dashboard, and recorded in the store's activity log with the app's name. Refused when the text holds a number (4 digits or more), an email address or a link that is not in the Emporiqa draft or the shop's own contacts, a bank or card number, or masked or removed text. At most 30 an hour and 200 a day per store. Needs the send permission as well. Needs the conversations permission and the store's switch for AI assistants in Settings > Security, and works only for stores the person owns.

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": {
      "store_id": "<store_id>",
      "email_id": "<email_id>"
    },
    "name": "send_customer_email_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe reply as it is sent, plain text. Empty sends the draft as it is.
email_idYesFrom the list of customer emails.
store_idYesThe store's store_id (not its name).

Output Schema

NameRequiredDescriptionDefault
statusYes
billingNocharged, no_credit (sent, not billed: no credit) or limit (sent, not billed: monthly cap).
sent_atNo
sent_toNo
email_idYes
store_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses billing impact, activity-log recording, content refusal rules (numbers of 4+ digits, foreign email addresses/links, bank or card numbers, masked text), rate limits of 30/hour and 200/day per store, and the permission plus Settings > Security toggle required. This is exactly the kind of invisible side-effect and rejection context the destructiveHint annotation cannot convey.

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?

Purpose comes first, then draft dependency, then billing/audit effects, then validation refusals, then limits and permissions — a sensible escalation. The sentences are long and multi-clause, which costs a bit of scanability, but no clause is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, rate-limited, permission-gated mutation with an output schema already covering return values, the description supplies everything needed to call it correctly or predict refusal: draft precondition, content rules, quotas, and required permissions. Nothing material is left implicit.

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 100%, so the baseline is 3; the description earns more by explaining that supplied text replaces the draft's words while omission sends the draft as-is, and by tying email_id to 'the address the email came from'. It does not add format detail for store_id beyond the schema's 'not its name' note.

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 ('Sends one reply to one customer email'), plus scope constraints — from the store's mailbox, to the originating address — and implicitly separates itself from drafting via 'text replaces the draft's words'. An agent can distinguish it from draft_customer_email_reply without opening either 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 hard precondition (only emails with a ready Emporiqa draft can be answered) and an ownership restriction (works only for stores the person owns), which tells the agent when the call will fail. It never names the drafting alternative explicitly, so routing guidance is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources