Skip to main content
Glama

update_google_campaign_budget

Update the daily budget of a live Google Ads campaign.

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": {
      "campaignId": "<campaignId>",
      "newDailyBudget": "<newDailyBudget>"
    },
    "name": "update_google_campaign_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesNumeric Google Ads campaign ID.
customerIdNo
newDailyBudgetYesNew daily budget in account currency.
loginCustomerIdNo
confirmHighBudgetNoRequired if newDailyBudget exceeds $500/day to confirm high budget spending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmHighBudget
      Added value: +{
      +  "description": "Required if newDailyBudget exceeds $500/day to confirm high budget spending.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only adds the constraint that the campaign must be 'live.' It does not say the change is immediately applied to the ad platform, whether it is reversible, what permissions or login context (loginCustomerId) are needed, or how currency is handled. The high-budget confirmation requirement is only revealed by the schema, not the description.

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?

A single front-loaded sentence with no filler or redundancy. Brevity is a virtue here, though the sentence is shorter than the tool's risk profile warrants.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a live-spend mutation with five parameters, two of them (customerId, loginCustomerId) undocumented anywhere, a conditional confirmation flag, and no annotations or output schema to fall back on. The description covers only the bare action, so an agent lacks the context to invoke it safely in the general case.

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%, so the schema documents campaignId, newDailyBudget, and confirmHighBudget including the $500/day threshold. The description adds only the notion of a daily budget in account currency and a 'live' campaign, leaving customerId and loginCustomerId undocumented in both places. Marginal value over the schema, so a middling score.

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?

States a specific verb and resource: 'Update the daily budget of a live Google Ads campaign.' An agent can tell this changes budget rather than status or publishing (unlike set_google_campaign_status or publish_campaign_to_google_ads). It stops short of naming any sibling or contrasting with budget-setting alternatives, so it is clear but not differentiating.

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?

There is no when-to-use guidance: nothing about preconditions (campaign must be live and already published), what to do for an unsaved campaign, or which sibling to use for status or publishing changes. The word 'live' hints at a precondition but does not tell the agent how to check or satisfy it.

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.

Resources