Skip to main content
Glama

Campaign stats

campaign_stats
Read-onlyIdempotent

Returns delivery and engagement numbers for a campaign: sent, delivered, bounced, complained, opened, clicked, unsubscribed and top links. Free and read only. Requires API key scope: read.

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": "campaign_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (a UUID), as returned by campaign_draft or campaigns_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description nonetheless adds value beyond them by disclosing that the call is "Free" and requires the read API key scope, neither of which appears in the annotations. It stops short of noting freshness/lag or whether unpublished campaigns return partial data, which would have pushed this higher.

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?

Two tight sentences: the first front-loads the returned fields, the second carries the access/cost constraints. No filler, no restatement of the title, and every clause carries information an agent would otherwise have to guess.

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?

For a one-parameter read tool with no output schema, the description compensates well by enumerating the metric set that will come back plus cost and scope conditions. The remaining gap is that it says nothing about the measurement window or whether stats are near-real-time, which matters for a reporting endpoint an agent may sequence around campaign_send_test or campaign_send.

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?

Schema description coverage is 100%: the single `id` parameter is documented as a UUID with a pattern and explicitly tied to campaign_draft or campaigns_list. The description adds no parameter-level meaning of its own, so this sits at the baseline where the schema does all the work.

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 description opens with a specific verb and resource ("Returns delivery and engagement numbers for a campaign") and then enumerates the exact metrics (sent, delivered, bounced, complained, opened, clicked, unsubscribed, top links), so an agent knows precisely what this returns. It reads as a per-campaign read operation, distinct from list/mutation siblings like campaigns_list or campaign_update.

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 implied by the scope of the returned metrics but never stated: there is no explicit "use this when..." guidance and no routing to alternatives such as campaigns_list for a catalog or campaign_preview for a preview. The one concrete prerequisite given ("Requires API key scope: read") is a useful qualifying condition, but it establishes permission rather than when-to-use.

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