Skip to main content
Glama

ADS Beast

campaign_analyze

Read-only

Deep analysis of one campaign: metrics, trends and recommendations. Takes up to a minute. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back days.
campaign_idYesADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds two traits not derivable from them: the call can take up to a minute, and it consumes one AI request. Those latency and cost disclosures are exactly the kind of pre-call context an agent needs; it could say more about failure modes, but the added value is real.

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?

Three short fragments, front-loaded with purpose, then runtime, then cost — no filler. The telegraphic 'AI: 1 AI request' notation is a little cryptic in isolation, but it stays out of the way.

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?

For an expensive read-only analysis tool with no output schema, the definition covers what it returns (metrics, trends, recommendations), how long it takes, and what it costs, and the schema fully documents both inputs. That is enough for an agent to decide and invoke correctly.

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 coverage is 100% and the schema already documents both parameters, including the important warning that campaign_id is the ADS Beast id rather than the platform's. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

'Deep analysis of one campaign' states a specific verb (analyze) and scope (one campaign), and the colon list 'metrics, trends and recommendations' tells the agent concretely what it produces. It stops short of naming any sibling (get_campaign, campaign_diagnose, campaign_history_analysis), so the agent must infer the 'deep vs shallow' distinction itself.

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 only implied: the word 'deep' and the runtime warning suggest this should be reserved for cases where a full analysis is wanted, but there is no explicit when-to-use, when-not, or named alternative for cheaper lookups like get_campaign. The agent is left to guess the routing rule.

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.