Skip to main content
Glama

ADS Beast

campaign_history_analysis

Read-only

What worked for a client before: average CPA and CTR, best campaigns and best audiences.

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": {
      "client_id": "<client_id>"
    },
    "name": "campaign_history_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 profile is covered. The description adds the useful behavioral fact that the tool returns historical aggregates and top performers, but says nothing about the time window covered, data freshness, or result size — meaningful for an open-world analysis.

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?

One short sentence, front-loaded with the core value proposition ('what worked for a client before') followed by the concrete metrics and outputs. No filler, though the fragment style and lack of a verb make it slightly less crisp than it could be.

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?

For a one-parameter read-only analysis with no output schema, the description conveys enough to know the return shape at a high level. It is not complete on temporal scope or how 'best' is ranked, which matters for interpreting results from an open-world analytical tool.

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 a single required parameter, client_id, with 0% schema description coverage. The description implies the client scoping but never explains what client_id refers to or where to obtain it; the parameter is intuitive enough that this is a modest gap rather than a blocking one.

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 the concrete output of the tool — average CPA and CTR plus best campaigns and best audiences for a given client — which is a specific, recognizable analysis rather than a restatement of the name. It is distinguishable from generic siblings like campaign_analyze or audit_campaign_health, though it never explicitly contrasts itself with them.

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 guidance on when to reach for this tool versus the many sibling analysis tools (client_market_analysis, audit_campaign_portfolio, campaign_diagnose). No preconditions beyond the required client_id are stated, and no exclusions are given.

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.