Google Ads MCP Server

get_budget_recommendations

Get actionable budget optimization recommendations for a specific Google Ads campaign to improve performance and allocate spend effectively.

Instructions

Get Google budget optimization recommendations

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

Input Schema

Name	Required	Description	Default
`campaignId`	Yes	Campaign ID
`customerId`	Yes	Google Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

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 responsibility for disclosing behavioral traits. It only restates the function without mentioning read-only nature, expected output format, dependencies, or side effects, which is insufficient.

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 description is a single focused sentence that is front-loaded and free of unnecessary words. It is efficient, though it lacks additional sections or guidance, which prevents a perfect score.

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?

For a tool with no annotations, no output schema, and only two parameters, the description should offer more context. It does not explain what the returned recommendations contain, how they are scoped, or any limitations, making the tool feel incomplete.

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?

Both parameters are fully described in the schema with clear names and descriptions, so the baseline is 3. The description adds no additional insight into parameter usage or formatting, so it does not exceed the baseline.

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 description clearly states the tool retrieves Google budget optimization recommendations. It is specific about the resource but does not explicitly differentiate from the sibling tool get_recommendations, which likely covers broader recommendation types.

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?

No usage context is provided. The description does not mention when to use this tool versus alternatives such as get_recommendations, apply_recommendation, or get_shared_budgets, leaving the agent without decision guidance.

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

Deploy Server