Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Email Campaign Stats

get-email-campaign-stats
Read-onlyIdempotent

Retrieve an email campaign's sent, delivered, bounced, open, click, unsubscribe, spam, conversion, and revenue metrics and rates to analyze performance.

Instructions

Get how one email campaign performed: sent, delivered and bounced counts, opens and clicks (total and unique), unsubscribes, spam complaints, their rates, clicks per link, and the conversions and revenue attributed to it. 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-email-campaign-stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe email campaign id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.5/5.0
Behavior5/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 substantive behavior beyond them: rate values are fractions 0–1, rates are null when the divisor is zero, totals are lifetime-cumulative, and recount cadence is 15 minutes for email. That staleness window is exactly the kind of detail an agent would otherwise misreport.

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?

Front-loaded with the metric inventory, then two compact sentences on rate encoding and freshness. With no output schema, the enumeration earns its space; there is no filler or repetition.

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?

No output schema exists, so the description must describe the return payload, and it does so thoroughly (delivery counts, unique vs. total opens/clicks, unsubscribes, complaints, per-link clicks, attributed conversions and revenue) plus the caveat about zeroed recent data. Nothing needed to call or interpret the result 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?

There is a single required parameter whose schema description is fully covered ("The email campaign id." with a UUID pattern), so the schema carries the load. The description adds no further meaning about the id beyond what the schema states, which is the expected baseline for 100% coverage.

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 email campaign performed") and then enumerates the exact metrics returned. The channel qualifier (email) distinguishes it from the push/SMS/in-app stats siblings without needing to open any 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 clear operational context: totals span the campaign's whole life and are recounted every 15 minutes, so a fresh campaign reading 0 should be re-checked rather than reported as a failure. It does not name an alternative (e.g. get-email-campaign for configuration vs. this for metrics), so it stops short of explicit when-not guidance.

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