Skip to main content
Glama
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA

Send Email Campaign

send-email-campaign
Destructive

Send or schedule an email campaign to subscribed contacts in its lists, tags and segments. Confirm the audience and content with the user first, since sent messages cannot be recalled.

Instructions

Send the email campaign now, or schedule it with scheduled_at. It goes to every subscribed contact in its lists, tags and segments. The campaign must be a draft or scheduled with every required field set. Call get-email-campaign first and show the user its content. Tell the user the audience: if you set it in this conversation, name those lists, tags and segments and their sizes (get-list, get-segment). The campaign's own record doesn't include its audience, so otherwise ask the user to confirm it in the Arsel dashboard. This reaches real people, and a message that has gone out cannot be recalled. Before calling it, show the user what will go out and to whom, and wait for their go-ahead. A scheduled, queued or sending campaign can be stopped with cancel-email-campaign.

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>"
    },
    "name": "send-email-campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe email campaign id.
scheduled_atNoISO 8601 date-time in the future, with the user's UTC offset (e.g. 2026-12-01T09:00:00+03:00 for Saudi Arabia), to schedule the campaign. Omit to send now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive and non-idempotent behavior, and the description adds substantial context beyond them: that the message reaches real people, cannot be recalled, that the campaign's own record omits its audience, and that consent should be obtained before sending. This is exactly the operational context an agent needs for an irreversible action.

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?

Front-loaded with the action and scheduling option, then preconditions, then the audience-confirmation rule, then a safety warning. Slightly dense with back-to-back imperatives, but every sentence carries distinct operational information.

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?

Covers purpose, prerequisites, audience-discovery path (get-list, get-segment), confirmation workflow, irreversibility, and the recovery route. No output schema exists, but the description does not need to explain return values for a send action.

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, and the description adds the decision semantics for `scheduled_at` (send now vs schedule) plus the associated timezone expectation implied by the schema. It doesn't repeat the UUID format, which is appropriately left to 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?

States a precise verb+resource pair ("Send the email campaign now, or schedule it with `scheduled_at`") and names the audience ("every subscribed contact in its lists, tags and segments"). It is clearly distinguishable from get-email-campaign, cancel-email-campaign and the push/SMS siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit preconditions are given: the campaign must be draft or scheduled with all required fields set, get-email-campaign must be called first, and the audience must be shown or confirmed before sending. It also names the correct alternative for stopping a queued or sending campaign (cancel-email-campaign).

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