Skip to main content
Glama

Google Ads: Set campaign budget

ads_set_campaign_budget
DestructiveIdempotent

Change a Google Ads campaign's daily budget. Give the amount in real currency (50 means $50.00/day) — the connector converts to micros. Returns the before value, the change, and the monthly impact. Previews unless confirm is true.

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": {
      "customer_id": "<customer_id>",
      "campaign_id": "<campaign_id>",
      "daily_budget_major": "<daily_budget_major>"
    },
    "name": "ads_set_campaign_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
campaign_idYes
customer_idYes
daily_budget_majorYesDaily budget in account currency, e.g. 50 for $50/day
acknowledge_large_changeNoRequired to raise a budget by more than 50% in one step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm / description
      Added value: +"Leave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), but the description adds real context beyond them: the currency-vs-micros conversion, the default preview behavior, and the exact return payload (before value, delta, monthly impact). It omits the large-change guardrail and any auth/permission requirements, which are documented only in the schema.

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, front-loaded with the action, then units, then return shape, then the preview/confirm rule. Every clause carries information and nothing is repeated from the schema.

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?

No output schema exists, and the description compensates by naming what is returned. Preview-by-default and unit conversion are covered, and annotations carry the safety profile. The only gap is the acknowledge_large_change precondition, which appears solely 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?

With 60% schema coverage, the description adds genuine meaning for daily_budget_major by explaining the micros conversion the connector performs ('50 means $50.00/day'), going beyond the schema's unit note. It does not clarify customer_id or campaign_id, but those are self-evident identifiers.

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 — 'Change a Google Ads campaign's daily budget' — and the platform qualifier distinguishes it from meta_set_campaign_budget and from sibling budget/bidding tools like ads_set_bidding_strategy. An agent can identify the operation and target without opening the schema.

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?

'Previews unless confirm is true' gives one actionable usage cue, but it largely duplicates what the confirm parameter description already states in the schema. There is no explicit guidance on when to use this vs. adjacent tools such as ads_campaign_bidding or ads_set_bidding_strategy, nor any stated prerequisite (e.g. permission level).

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.