Google Ads MCP Server

list_budgets

Read-only

Retrieve campaign budgets from a Google Ads account by customer ID to review spending limits and budget allocations, with an optional result limit.

Instructions

List campaign budgets in the account.

Args:
    customer_id: Google Ads customer ID.
    limit: Max budgets to return (default 100).

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": "list_budgets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`customer_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds essentially nothing beyond that. It does not mention pagination behavior, whether all budgets or only campaign-attached budgets are returned, account-level access requirements, or any rate limits for a list operation.

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?

One-sentence summary followed by an Args block is well front-loaded and free of filler. The Args entries largely restate parameter names, so they are slightly padded but not harmful.

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

Completeness3/5

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

For a simple read-only two-parameter list tool with a full input schema and annotations covering safety, the definition is close to adequate. The main gap is that with no output schema, an agent gets no signal about what a budget record contains (amount, period, campaign association).

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 description coverage is 0%, so the description must carry the burden, and it does partially: it clarifies customer_id is a Google Ads customer ID (a format hint the bare title lacks) and explains limit as max budgets returned. However, it omits the customer ID format/prefix convention and whether limit has an upper bound or interacts with pagination.

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?

"List campaign budgets in the account" gives a specific verb (list) and resource (campaign budgets) scoped to an account, which is clearly distinct from siblings like create_budget or get_budget_utilization. It stops short of explicitly contrasting with list_campaigns or any budget-related alternative.

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 guidance on when this tool is the right choice versus list_campaigns (which may also surface budget info) or get_budget_utilization for spend analysis. No prerequisites, pagination expectations, or exclusions are stated.

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

Deploy Server