Skip to main content
Glama

ADS Beast

campaign_strategy_expert_review

Read-only

Six specialist viewpoints (media buyer, copywriter, audience, competitors, conversion, data) on a planned campaign. Takes up to a minute. AI: 1 AI request. May return a job_id (get_job_result).

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_strategy_expert_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.UA
platformNoboth
client_idYes
objectiveNoleads, sales, traffic or awareness.leads
extra_contextNoAnything the reviewers should know.
budget_monthlyNoPlanned monthly budget in the account currency, whole units.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing latency (up to a minute), AI-credit cost (1 AI request), and the asynchronous handoff where a job_id may come back and get_job_result must be called. That async/cost behavior is exactly the kind of thing the schema and annotations cannot convey.

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 sentences, front-loaded with the core value proposition, then latency, cost, and the job_id handoff. The telegraphic "AI: 1 AI request" phrasing is terse but earns its place as a cost signal.

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

Completeness4/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 could say more about the shape of the review returned, which is the main gap. Against that, it covers the essentials for a read-only, open-world, potentially slow call: what it analyzes, timing, cost, and the follow-up job lookup, which is enough for correct invocation.

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 67% with six parameters, so the schema does most of the work on geo, platform, objective and budget. The description adds no meaning beyond it — for example, it never explains how extra_context influences the reviewers or how platform="both" changes the output — so 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?

The description names a concrete verb-like action (produces six specialist viewpoints) and enumerates the six personas, so an agent knows exactly what it gets back conceptually. It does not, however, distinguish itself from the sibling campaign_strategy_generate, leaving the generate-vs-review split for the agent to infer.

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?

"On a planned campaign" implies the precondition that a campaign plan already exists, which is useful context. There is no explicit when-not, and no routing statement toward campaign_strategy_generate or the audit_* tools, so usage must be inferred.

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.