Skip to main content
Glama

ADS Beast

campaign_diagnose

Read-only

Works through the possible causes of one KPI problem in a campaign: audience saturation, creative fatigue, landing page, bid strategy, seasonality, tracking.

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>",
      "problem": "<problem>"
    },
    "name": "campaign_diagnose"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a non-destructive read-only tool, so the description need not repeat safety details. It adds meaningful context by enumerating the six cause areas it will examine, which tells the agent how broad the diagnosis is. It does not disclose whether results are hypotheses, ranked causes, or recommendations, nor how expensive the analysis is.

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?

A single well-formed sentence with the action front-loaded and the cause categories efficiently listed afterward. There is no filler, though 'works through' is slightly informal and the list is dense.

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?

The tool has three well-described parameters and no output schema, so the description should ideally say what a diagnosis produces (e.g., likely causes, ranked hypotheses, recommendations). It covers scope of analysis but not result shape or depth. For a read-only diagnostic this is adequate but incomplete.

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 explains all three parameters, including that campaign_id is an ADS Beast id rather than a platform id. The description mentions 'one KPI problem' but adds no syntax, format, or interpretation guidance beyond the schema. A baseline 3 is appropriate when the schema carries parameter meaning.

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?

States a specific diagnostic action on a well-scoped resource: one KPI problem in one campaign. The colon-list of cause categories (audience saturation, creative fatigue, landing page, bid strategy, seasonality, tracking) makes the tool's remit concrete. It does not explicitly differentiate itself from near siblings like audit_campaign_health, but the single-KPI framing is clear.

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?

The phrase 'one KPI problem' implies this tool should be used when a specific symptom needs explaining, which is useful context. However, it never states when to prefer this over broader tools such as audit_campaign_health or campaign_analyze, and gives no exclusions or prerequisites. Usage is left to inference.

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.