Skip to main content
Glama

How a campaign landed

campaign_insights
Read-onlyIdempotent

Delivery and engagement for one campaign: sent, delivered, read, replied, failed. Answers 'how did it do' without reading the recipient list.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "campaign_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign id, as returned by campaign_list"New value: +"The campaign's id"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely new behavioral information: the result is an aggregate summary for a single campaign rather than a per-recipient enumeration, which shapes how an agent should consume the output.

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 short sentences, zero filler. The core purpose and the returned metric names are front-loaded, and the disambiguating clause about the recipient list follows immediately after.

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?

With no output schema, the description compensates by enumerating the metrics returned (sent, delivered, read, replied, failed), so an agent knows what to expect without calling the tool. Combined with annotations covering the safety and idempotency profile, nothing essential for correct invocation 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 exactly one parameter and schema description coverage is 100%, so the schema already carries the full burden of explaining campaignId. The description adds no format, sourcing, or validation detail beyond what the schema states, which matches the baseline for a fully described single-parameter schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (one campaign) and a specific output (delivery and engagement metrics), and enumerates them: sent, delivered, read, replied, failed. The phrase 'without reading the recipient list' implicitly separates it from a per-recipient detail view, though it does not name campaign_detail directly.

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?

It gives a clear use case (answering 'how did it do') and contrasts that with paging through a recipient list, which is the practical alternative. It stops short of explicitly naming a sibling tool or stating when not to use it, so it falls below the top of the scale.

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.