Skip to main content
Glama

Send test email

campaign_send_test

Sends a test copy of a draft to up to 3 addresses. The addresses must belong to users of this workspace; other addresses are refused. Uses quota only for the test emails actually sent, does not touch the audience, and does not change the draft. Offer this after campaign_preview so the person can check it in their own inbox. Requires API key scope: draft.

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": {
      "id": "<id>",
      "to": "<to>"
    },
    "name": "campaign_send_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (a UUID), as returned by campaign_draft or campaigns_list.
toYes1 to 3 addresses of people who use this workspace.

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?

Beyond the annotations, the description discloses quota consumption semantics ("uses quota only for the test emails actually sent"), side-effect boundaries ("does not touch the audience, and does not change the draft"), recipient eligibility with refusal behavior, and a required API key scope. This is exactly the mutation/scope context an agent needs and that readOnlyHint/openWorldHint alone do not convey.

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 short sentences, front-loaded with what the tool does, then constraints, then side effects, then sequencing. Nothing is redundant filler and each sentence carries a distinct decision-relevant fact.

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?

There is no output schema, so the description is the only place to learn what comes back; it does not say whether the response reports per-address success/failure or just an aggregate confirmation, which matters when some addresses are refused. Everything else needed to call the tool correctly is present.

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% and both parameters are documented there, so the baseline is 3; the description adds value by stating that non-workspace addresses are actively refused, which explains the failure mode the email/number constraints imply. It does not otherwise extend parameter meaning beyond the schema.

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?

The opening sentence gives a specific verb and resource ("Sends a test copy of a draft") plus scope ("to up to 3 addresses"), which separates it from real sends like email_send and from read-only campaign_preview. 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?

Explicit sequencing guidance is given ("Offer this after campaign_preview so the person can check it in their own inbox"), plus a hard eligibility rule that recipients must be workspace users. It does not state when NOT to use it (e.g. as a substitute for a real send via campaign_schedule), which keeps it short of a 5.

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