Skip to main content
Glama

ADS Beast

campaign_strategy_generate

Read-only

A strategic plan for a client over a horizon: channels, budget split, KPI targets and launch phases. 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_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNogrowth, efficiency or brand.
client_idYes
horizon_monthsNoPlanning horizon, 1-12 months.

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?

The description adds behavior the annotations do not: expected latency ('up to a minute'), cost ('1 AI request'), and asynchronous possibility with the required polling tool. That is valuable operational context for an openWorldHint tool. It omits failure/rate-limit behavior and whether the job is always async or only sometimes, keeping it at 4.

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 tight sentences with the deliverable front-loaded, then latency/cost, then the async escape hatch. The telegraphic 'AI: 1 AI request' fragment is slightly cryptic but wastes no space.

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 carries the return burden and does so by enumerating the plan's components plus the job_id case. For a 3-parameter tool this is close to sufficient; only error and non-job return shapes are unaddressed.

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 67%, so the schema already documents focus values and the horizon range. The description reinforces horizon and client scoping ('for a client over a horizon') but adds nothing about focus or client_id semantics. Baseline 3 is appropriate given the schema does most of the work.

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 states a concrete deliverable: a strategic plan for a client covering channels, budget split, KPI targets and launch phases, scoped by a planning horizon. That is specific enough to separate it from audit/draft/publish siblings. It stops short of naming a sibling it is not, so a 4 rather than a 5.

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 implied by the artifact described, and the 'May return a job_id (get_job_result)' line gives a concrete follow-up path — useful routing. However, there is no explicit when-to-use vs. when-not guidance and no mention of campaign_strategy_expert_review, the obvious adjacent tool, nor any prerequisite for client_id.

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.