Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get SMS Campaign Stats

get-sms-campaign-stats
Read-onlyIdempotent

Retrieve SMS campaign performance metrics—recipients, delivery status counts, clicks, conversions, and attributed revenue—to evaluate delivery outcomes and campaign results.

Instructions

Get how one SMS campaign performed: recipients, a count per delivery status (delivered, undelivered, failed, blocked, rejected, expired, pending), clicks, and the conversions and revenue attributed to it. clicks leaves out link scanners, which are counted in bot_clicks. Rates are fractions from 0 to 1, so 0.25 is 25%, and null while there is nothing to divide by. Totals cover the whole life of the campaign and are recounted periodically (every 15 minutes for email), so a campaign sent minutes ago can still read 0: check again later rather than reporting that nothing was delivered.

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": "get-sms-campaign-stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe SMS campaign id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine behavioral context beyond them: totals cover the campaign's whole life, are recounted periodically, and can legitimately read 0 for a just-sent campaign. That staleness caveat is exactly the kind of trait an agent could not infer; the only blemish is the stray '(every 15 minutes for email)' in an SMS tool, which muddies the freshness guarantee.

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 payload summary, then rate/number semantics, then the freshness caveat — a sensible ordering with little filler. It runs long for one operation, and the accidental email reference is wasted or misleading 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?

With no output schema, the description does the necessary work of naming the return fields, explaining that rates are 0-1 fractions and null when undividable, and clarifying that clicks excludes scanner traffic counted in bot_clicks. Missing only minor shape details, and clouded by the email-specific freshness note.

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?

There is a single required parameter whose schema description coverage is 100% ('The SMS campaign id' with a UUID pattern), so the schema carries the semantics fully. The description adds no format or sourcing detail for the id beyond saying there is one campaign, leaving this at the baseline.

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 ('Get how one SMS campaign performed') and enumerates the returned content: recipients, per-status delivery counts, clicks, conversions and revenue. An agent can distinguish this from get-sms-campaign (configuration) or list-sms-campaigns (enumeration) 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 Guidelines3/5

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

Usage is only implied by 'one SMS campaign' — there is no explicit statement of when to call this versus get-sms-campaign or the list endpoint. It does give one useful operational rule ('check again later rather than reporting that nothing was delivered'), but it addresses interpreting results, not tool selection.

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