Google Ads MCP Server

create_budget

Creates a campaign budget with daily amount, delivery method, and sharing options. Shows a preview first and requires confirmation, refusing amounts above the configured daily spend cap.

Instructions

Create a new campaign budget.

Safety: returns a preview first. Call again with confirm=True to create it.
Refused if the amount is above GOOGLE_ADS_MAX_DAILY_BUDGET.

Args:
    customer_id: Google Ads customer ID.
    name: Budget name.
    amount: Daily budget amount in currency (e.g., 50.00 for $50/day).
    delivery_method: 'STANDARD' (spread evenly) or 'ACCELERATED'.
    explicitly_shared: If True, budget can be shared across multiple campaigns.
    confirm: Must be True to actually create the budget (after reviewing the preview).

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>",
      "name": "<name>",
      "amount": "<amount>"
    },
    "name": "create_budget"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`amount`	Yes
`confirm`	No
`customer_id`	Yes
`delivery_method`	No	STANDARD
`explicitly_shared`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false; the description adds the non-obvious two-step preview/confirm protocol and an environmental refusal condition (max daily budget cap), which materially change how an agent must call it. This is exactly the kind of behavior structured fields cannot express.

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?

The safety protocol is front-loaded before the Args block, which is the right ordering, and the Args list is scannable. Slight redundancy: confirm is explained both in the Safety section and again in Args.

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 mutation tool with no output schema and 6 undocumented-in-schema parameters, the description covers the creation flow, gating mechanism, and all arguments. It doesn't say what the preview or success response contains (e.g., a budget resource name/ID), which an agent would need to chain into create_campaign.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: it defines every one of the 6 parameters, including the currency/units convention for amount ('50.00 for $50/day'), the two literal values for delivery_method, and the operational meaning of confirm. Only minor gaps remain (no format example for customer_id).

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 line gives a specific verb and resource ('Create a new campaign budget'), which is immediately distinguishable from update_budget and get_budget_utilization. It stops short of explicitly naming those siblings as alternatives, so a 4 rather than a 5.

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?

The description gives concrete operating guidance: it returns a preview first, must be re-called with confirm=True to actually create, and is refused if the amount exceeds GOOGLE_ADS_MAX_DAILY_BUDGET. What's missing is routing guidance against update_budget (i.e., use this only when no budget exists yet).

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

Deploy Server