Skip to main content
Glama

ADS Beast

campaign_swarm_runs

Read-only

Recent multi-agent campaign generation runs with status, platform and budget.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "campaign_swarm_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety and external-dependency profile is covered. The description adds that records carry status, platform and budget, which hints at returned fields, but says nothing about ordering, recency window, default limit behavior, or whether client_id scoping is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no filler, so nothing is wasteful. However, brevity here reflects under-specification rather than front-loaded clarity, since key information (that it lists, what it returns, how limit/client_id behave) is absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple two-parameter, non-nested read tool whose annotations carry the safety profile, which lowers the bar. With no output schema, though, the description should indicate the return shape more concretely and explain the undocumented client_id; as written it only gestures at fields returned per run.

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 50%: limit is documented in the schema while client_id is not, and the description does not explain what client_id scopes. The mention of 'status, platform and budget' refers to output fields, not the two input parameters, so it adds no parameter meaning beyond the schema; baseline 3 applies for a two-parameter tool with partial coverage.

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

Purpose3/5

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

The description is a noun phrase rather than a verb+resource statement, so it identifies the resource ('recent multi-agent campaign generation runs') but never says it lists them. It distinguishes the resource from siblings like audit_campaign_health or create_campaign_draft, but an agent must infer that this is a read/list operation from the annotation title 'List campaign generation runs'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this for inspecting recent generation runs versus campaign_history_analysis or campaign_dashboard_summary. No prerequisites, no exclusions, and no routing to alternatives are given, leaving the agent to guess from the name alone.

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.