Skip to main content
Glama

ADS Beast

Propose a campaign change (pause, enable, budget)

propose_campaign_change

Create a change proposal for a campaign. Nothing changes in the ad account until a person approves the proposal in ADS Beast or in Telegram; the proposal expires on its own if nobody decides. State the reason with the numbers behind it.

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>",
      "change": "<change>",
      "reason": "<reason>"
    },
    "name": "propose_campaign_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYes
reasonYesWhy - with the figures the person should check.
client_idNo
new_budgetNoNew monthly budget in the account currency; change_budget only.
campaign_idYesADS Beast campaign id (from list_campaigns).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: nothing changes in the ad account until a human approves in ADS Beast or Telegram, and the proposal self-expires if undecided. That human-in-the-loop gate and auto-expiry are exactly the non-obvious facts an agent needs, and they are consistent with destructiveHint=false. It does not say how long before expiry or what a successful call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose first, then the safety/approval constraint, then the reason requirement. Every sentence carries information an agent would not otherwise have, with no padding.

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?

For a five-parameter mutation with no output schema, the description covers the crucial part (nothing is applied without approval, and proposals expire). Gaps remain around return values, expiry timing, and the missing distinction from the prepare_* siblings, but nothing essential to calling it correctly is absent.

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 60% and the description reinforces 'reason' by asking for the figures behind it, which adds intent beyond the schema's wording. However, the change enum values, new_budget applicability, and client_id are never clarified in the description, leaving the weakest-documented parameters to the schema alone.

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?

A specific verb plus resource: 'Create a change proposal for a campaign.' An agent immediately knows this stages a change rather than applying one. It never names the closely named siblings (prepare_campaign_pause, prepare_campaign_enable, prepare_campaign_budget_change) or explains how a proposal differs from a prepared change, so sibling differentiation is left to inference.

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?

The description explains the approval workflow but gives no when-to-use or when-not-to-use criteria. With siblings named prepare_campaign_pause / prepare_campaign_enable / prepare_campaign_budget_change covering the same three actions, an agent gets no signal about which entry point to pick.

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.