Google Ads MCP Server

create_performance_max_campaign

Create a Performance Max campaign in Google Ads by specifying customer ID, campaign name, daily budget, and optional bidding strategy and targets.

Instructions

Create a Performance Max 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": {
      "customerId": "<customerId>",
      "name": "<name>",
      "budgetAmountMicros": "<budgetAmountMicros>"
    },
    "name": "create_performance_max_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign name
`customerId`	Yes	Google Ads customer ID
`targetRoas`	No
`targetCpaMicros`	No
`budgetAmountMicros`	Yes	Daily budget in micros
`biddingStrategyType`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.2/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states 'Create a Performance Max campaign' with no mention of required settings, side effects, or potential configuration steps. For a creation tool, this transparency is severely lacking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified rather than concise—it repeats the tool name without adding value. A concise description would pack necessary context into few words, but this one omits essential information and does not earn its place.

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

Completeness1/5

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

For a 6-parameter creation tool with no output schema and no annotations, a single sentence is grossly incomplete. The description does not explain what happens after creation, what the campaign requires (e.g., asset groups), or any return values, making it insufficient for reliable invocation.

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

Parameters2/5

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

The schema provides descriptions for only 3 of 6 parameters (50% coverage), leaving targetRoas, targetCpaMicros, and biddingStrategyType undocumented. The description adds no parameter information and does not compensate for the gaps, so the agent must infer meaning from names and enums alone.

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 action ('Create') and the specific resource ('Performance Max campaign'), which distinguishes it from other campaign creation tools by campaign type. However, it simply restates the tool name and does not elaborate on what a Performance Max campaign entails or how it differs from alternatives.

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 to use this tool versus alternatives such as create_campaign, create_demand_gen_campaign, or create_app_campaign. The description does not mention prerequisites, exclusions, or typical use cases, leaving the agent without context for selection.

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

Deploy Server