google-ads-mcp

Overview Schema Source Related Servers Discussions Admin

create_performance_max_campaign

Create a Performance Max campaign in one atomic operation with budget, asset group, and paused status. Includes all required assets to meet PMax specs for activation.

Instructions

Create a complete Performance Max campaign with budget, campaign, and asset group.

Creates everything in a single atomic batch operation using temporary IDs. Campaign is created as PAUSED by default for safety.

PMax minimum requirements:

3+ headlines (max 30 chars each)
1+ long headlines (max 90 chars)
2+ descriptions (max 90 chars each)
1 business name
Final URLs
Image assets should be pre-uploaded (use asset resource names)

Args: customer_id: Google Ads customer ID. campaign_name: Campaign name. budget_amount: Daily budget in currency. asset_group_name: Name for the asset group. final_urls: Landing page URLs. headlines: 3-15 headlines (max 30 chars each). long_headlines: 1-5 long headlines (max 90 chars each). descriptions: 2-5 descriptions (max 90 chars each). business_name: Business name for the asset group. marketing_image_assets: Landscape image asset resource names (1200x628). square_image_assets: Square image asset resource names (1200x1200). logo_assets: Logo image asset resource names. youtube_video_assets: YouTube video asset resource names. bidding_strategy: 'MAXIMIZE_CONVERSIONS' or 'MAXIMIZE_CONVERSION_VALUE'. target_cpa: Target CPA (for maximize_conversions with target). target_roas: Target ROAS (for maximize_conversion_value with target). status: Initial status -- 'PAUSED' (default) or 'ENABLED'.

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>",
      "campaign_name": "<campaign_name>",
      "budget_amount": "<budget_amount>",
      "asset_group_name": "<asset_group_name>",
      "final_urls": "<final_urls>",
      "headlines": "<headlines>",
      "long_headlines": "<long_headlines>",
      "descriptions": "<descriptions>",
      "business_name": "<business_name>"
    },
    "name": "create_performance_max_campaign"
  }
}

Input Schema

Name	Required	Default
`status`	No	PAUSED
`headlines`	Yes
`final_urls`	Yes
`target_cpa`	No
`customer_id`	Yes
`logo_assets`	No
`target_roas`	No
`descriptions`	Yes
`budget_amount`	Yes
`business_name`	Yes
`campaign_name`	Yes
`long_headlines`	Yes
`asset_group_name`	Yes
`bidding_strategy`	No	MAXIMIZE_CONVERSIONS
`square_image_assets`	No
`youtube_video_assets`	No
`marketing_image_assets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, the description adds meaningful behavioral details: it creates everything atomically using temporary IDs, defaults to PAUSED for safety, and requires images to be pre-uploaded. This gives an agent useful operational context without contradicting the annotations.

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 well-structured: purpose first, then safety/behavior, then requirements, then an Args list. It is longer than average but justified by the complexity of a 17-parameter composite creation tool. A few parameter one-liners like 'Campaign name.' add little, but the overall structure is efficient.

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 complex creation tool with no output schema, the description covers inputs, defaults, prerequisites, and safety behavior thoroughly. It does not explain return values or clarify edge cases like conflicting target_cpa/target_roas with bidding_strategy, but these are relatively minor given the strength of the rest.

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 delivers. It documents all 17 parameters with practical semantics, including ranges, char limits, dimensions, business constraints, and bidding-strategy-specific targets like target_cpa and target_roas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create a complete Performance Max campaign with budget, campaign, and asset group.' It clearly explains the tool's scope and distinguishes it from generic campaign tools by emphasizing the atomic batch creation of all three components.

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 clear context for when to use this tool: you need a complete Performance Max campaign and want everything created in one atomic operation. It also lists PMax minimum requirements and notes that image assets should be pre-uploaded, which serves as a precondition. It does not explicitly name alternatives like create_campaign or add_assets_to_group, so it stops short of a 5.

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

Deploy Server