Skip to main content
Glama

Get Campaign Stats

get_campaign_stats
Read-onlyIdempotent

[Read · free] Summary stats for a Constellation campaign: target count, entry count, outreach volume, and acceptance / reply rates broken down by pool (coworker / engager / mutual) and composite-score tier. Outcomes logged for people who are not campaign entries are counted under an unattributed bucket in both by_pool and by_tier, so breakdowns always sum to the totals. Free — costs 0 credits.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_campaign_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesCampaign id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=false, destructive=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the call costs 0 credits, and outcomes for people who are not campaign entries are folded into an `unattributed` bucket so by_pool and by_tier breakdowns always reconcile to the totals — an aggregation invariant an agent could not infer from structured fields alone.

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?

Two tight sentences with the cost/safety tag front-loaded so an agent can triage quickly. The only waste is mild redundancy between the `[Read · free]` prefix and the trailing 'Free — costs 0 credits', which restates the same 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?

With no output schema, the description carries the burden of describing returns, and it does so by naming each metric and both breakdown axes plus the reconciliation rule for unattributed outcomes. It stops short of describing the shape of the response (e.g., nested by_pool/by_tier objects or value types), but for a single-parameter read tool this is close to complete.

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?

There is a single required parameter with 100% schema description coverage, so per the baseline this scores 4. The description adds no additional meaning about campaign_id (format, sourcing, or validation) beyond the schema's uuid format, but none is needed for a one-parameter lookup.

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 (get) and resource (stats for a Constellation campaign) and enumerates exactly what is returned: target count, entry count, outreach volume, and acceptance/reply rates. It further specifies the two breakdown dimensions (pool and composite-score tier), so an agent knows precisely what this tool produces without consulting siblings.

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 rather than stated: it is a read-only, free call for a single campaign's performance metrics, and the `[Read · free]` prefix signals it is a cheap lookup. However, it never says when to prefer this over alternatives such as get_usage_history or get_credit_balance, nor does it state prerequisites (e.g., that campaign_id must reference an existing campaign).

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