Skip to main content
Glama

ADS Beast

prepare_campaign_budget_change

Prepare a new monthly budget for one campaign. new_monthly_budget is in the ad account's own currency, in whole units (3000 means 3000.00, never cents or micros); the preview shows the daily amount and the exact figure the platform will receive. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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>",
      "new_monthly_budget": "<new_monthly_budget>",
      "reason": "<reason>"
    },
    "name": "prepare_campaign_budget_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
currencyNoISO code of the currency you believe the account uses, for example EUR. Optional safety check: the call is refused when it differs from the account's currency.
campaign_idYesADS Beast id from list_campaigns, not the platform's.
new_monthly_budgetYesNew monthly budget in the ad account's currency, whole units. 3000 means 3000.00 of that currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it declares no state change occurs, discloses that a preview_id is stored with a 15-minute single-use lifetime, and says the preview renders the daily amount and the exact figure the platform will receive. This reconciles the apparently odd readOnlyHint=false with the fact that only a stored preview is written.

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 with the purpose first, the units trap second, and the non-mutation/preview contract last. Every clause carries information the agent needs; nothing is padding.

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

Completeness5/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 still covers what the agent needs: the return artifact (preview_id), its lifetime and single-use constraint, what the preview displays, and the mandatory follow-up call. All four parameters are documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds a real guardrail by warning that values are whole currency units and 'never cents or micros', reinforcing the highest-risk unit-error case in new_monthly_budget.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Prepare a new monthly budget') and constrains scope to 'one campaign', which cleanly separates it from sibling preparers such as prepare_campaign_bid_strategy_change or prepare_campaign_pause.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the two-step workflow explicit: this tool changes nothing, returns a preview_id, and the agent must then call execute_prepared_change. It does not spell out when to prefer a different approach or what to do if the preview looks wrong, but the intended usage path is unambiguous.

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.