Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_create_asset_group

Create an asset group for a Performance Max campaign by providing headlines, descriptions, long headline, and linking existing image assets.

Instructions

Create an asset group for a Performance Max campaign.

Asset groups contain the creative assets (images, videos, text) that Performance Max uses across different Google channels.

PMax requires text assets AND image assets at creation time. Provide headlines, descriptions, long headline, and link existing image assets.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) campaign_id: Performance Max campaign ID asset_group_name: Name for this asset group final_urls: Comma-separated list of landing page URLs headlines: List of headlines (3-15, max 30 chars each) descriptions: List of descriptions (2-5, max 90 chars each) long_headline: Single long headline (max 90 characters) existing_assets: List of existing assets to link, each with 'resource_name' and 'field_type' (e.g. MARKETING_IMAGE)

Returns: Asset group creation result

Example: google_ads_create_asset_group( customer_id="1234567890", campaign_id="12345678", asset_group_name="Main Products", final_urls="https://example.com/products", headlines=["Buy Now", "Shop Today", "Free Shipping"], descriptions=["Shop the latest products", "Quality guaranteed"], long_headline="Shop Our Complete Product Line Today" )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaign_idYes
asset_group_nameYes
final_urlsYes
headlinesNo
descriptionsNo
long_headlineNo
existing_assetsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses creation behavior and parameter constraints but lacks information on idempotency, error handling, authentication, or quotas. The output is mentioned but not detailed.

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?

The description is well-structured with a clear intro, requirement note, parameter list with descriptions, return line, and example. It is concise and front-loaded with the main purpose.

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?

Given 8 parameters and presence of output schema, the description covers purpose, requirements, and parameter details thoroughly. It lacks behavioral context like error scenarios, but overall completeness is high.

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%, yet the description provides thorough parameter explanations including constraints (e.g., headlines: 3-15, max 30 chars; customer_id: 10 digits, no hyphens). This compensates fully for the schema gap.

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 explicitly states 'Create an asset group for a Performance Max campaign' and explains the role of asset groups in PMax. It distinguishes this tool from siblings like google_ads_create_campaign or google_ads_create_ad_group by focusing on asset group creation and its requirements.

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?

The description mentions PMax requirements but does not explicitly state when to use this tool versus alternatives (e.g., after creating a PMax campaign). It provides context but no why or when-not guidance.

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/johnoconnor0/google-ads-mcp'

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