Skip to main content
Glama

create_pmax_campaign

Destructive

Create Google Ads Performance Max campaigns by supplying headlines, descriptions, images, and budget. Streamline campaign setup and improve ad performance.

Instructions

Create a Google Ads Performance Max campaign. Requires images, headlines, descriptions, and a business name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logo_urlNoURL to square logo (min 128x128)
final_urlYesLanding page URL
headlinesYesHeadlines (3-15, max 30 chars each)
target_cpaNoTarget CPA in USD (optional)
geo_targetsNoGeo target codes
daily_budgetYesDaily budget in USD
descriptionsYesDescriptions (2-5, max 90 chars each)
business_nameYesBusiness name (max 25 chars)
campaign_nameYesName for the campaign
long_headlineYesLong headline (max 90 chars)
square_image_urlNoURL to 1200x1200 square image
landscape_image_urlNoURL to 1200x628 landscape image
Behavior2/5

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

Annotations indicate destructiveHint: true, consistent with creating a campaign. However, the description adds no further behavioral context such as cost implications, immediate activation, or required permissions. With annotations, the bar is lower, but still lacks meaningful disclosure.

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

Conciseness5/5

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

Single, well-front-loaded sentence with no fluff. Every word serves to convey the tool's purpose and key requirements.

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?

No output schema and description does not mention return values (e.g., campaign ID). For a complex creation tool with 12 parameters, more context about success indicators or error states would be beneficial.

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 100%, so the schema already documents all 12 parameters. The description highlights a subset of required inputs but does not add meaning beyond what's in the schema. Baseline of 3 is appropriate.

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?

Description clearly states the tool creates a Google Ads Performance Max campaign and lists required elements (images, headlines, descriptions, business name). This distinguishes it from siblings like create_search_campaign or create_display_campaign.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for Performance Max campaigns but does not explicitly state when to use it versus alternatives or provide exclusions. No guidance on prerequisites like having a Google Ads account or linked advertisers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jshorwitz/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server