Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_set_campaign_budget

Destructive

Change a Google Ads campaign's daily budget in account currency; use validateOnly for a dry run and confirm the amount first because shared budgets affect all campaigns using them.

Instructions

Change a campaign's daily budget (in account currency). Shared budgets affect every campaign using them. Use validateOnly=true to dry-run. Always confirm the amount with the user first.

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": {
      "customerId": "<customerId>",
      "campaignId": "<campaignId>",
      "dailyBudget": "<dailyBudget>"
    },
    "name": "ads_set_campaign_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYes
customerIdYesGoogle Ads customer ID (with or without dashes)
dailyBudgetYes
validateOnlyNo
loginCustomerIdNoManager (MCC) ID if accessing through a manager; defaults to ads.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real blast-radius detail: shared budgets affect every campaign using them, and the amount is interpreted in account currency. That is exactly the kind of consequence information annotations cannot convey. It does not discuss propagation timing or failure behavior, keeping it below a 5.

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 short sentences, each with a distinct job: what changes, the shared-budget consequence, and the safe-invocation procedure. The core action and blast risk are front-loaded with no filler.

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 destructive single-field mutation with no output schema and safety already declared in annotations, this covers currency, scope of impact, dry-run, and user confirmation. Only minor gaps remain, such as whether the change applies immediately or how a shared budget's scope maps to campaignId.

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 only 40%, and the description compensates meaningfully: it specifies that dailyBudget is denominated in account currency and explains validateOnly as a dry-run switch, neither of which is in the schema. campaignId and loginCustomerId get no added meaning from the description, but loginCustomerId is documented in the schema.

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 first sentence names a specific verb and resource ('Change a campaign's daily budget') and adds a unit qualifier ('in account currency'), which is enough to separate it from siblings like ads_set_status or ads_campaign_performance. It stops short of explicitly naming an alternative sibling, but the operation is unambiguous.

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?

It gives two concrete operating instructions: use validateOnly=true as a dry-run, and confirm the amount with the user beforehand. There is no explicit when-not guidance (e.g., removing a budget, or what to do if the budget is shared), so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.