AdCopilot

Google Ads: create asset group

create_asset_group

Destructive

Creates an asset group for a Performance Max campaign and links all provided assets to it.

Asset groups and their assets must be created together in a single batch request.
Create all required assets first using create_text_asset, create_image_asset, etc.,
then pass their resource names here.

Minimum asset requirements for Performance Max:
- At least 3 headlines (max 15)
- At least 2 descriptions (max 5)
- At least 1 long headline (max 5)
- At least 1 marketing image (landscape, 1200x628 recommended)
- At least 1 square marketing image (1200x1200 recommended)
- At least 1 logo (1200x1200 recommended)
- YouTube videos are optional but recommended

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    campaign_id: The ID of the Performance Max campaign.
    name: Name for the asset group.
    final_url: The landing page URL for the asset group.
    headline_asset_resource_names: List of text asset resource names for headlines (min 3).
    description_asset_resource_names: List of text asset resource names for descriptions (min 2).
    long_headline_asset_resource_names: List of text asset resource names for long headlines (min 1).
    marketing_image_asset_resource_names: List of image asset resource names for landscape images (min 1).
    square_marketing_image_asset_resource_names: List of image asset resource names for square images (min 1).
    logo_asset_resource_names: List of image asset resource names for logos (min 1).
    youtube_video_asset_resource_names: List of YouTube video asset resource names. Optional.
    final_mobile_url: Mobile landing page URL. Optional.
    path1: First URL path text (max 15 characters). Optional.
    path2: Second URL path text (max 15 characters). Optional.
    status: Asset group status. One of: ENABLED, PAUSED. Default: ENABLED.
        In a campaign that is already running, an ENABLED asset group
        serves, from that campaign's budget, as soon as Google approves
        its assets; pass PAUSED to hold it.

Returns:
    Dictionary with the created asset group resource name and linked asset count.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`path1`	No
`path2`	No
`status`	No	ENABLED
`final_url`	Yes
`campaign_id`	Yes
`customer_id`	Yes
`final_mobile_url`	No
`logo_asset_resource_names`	No
`headline_asset_resource_names`	Yes
`description_asset_resource_names`	Yes
`long_headline_asset_resource_names`	Yes
`youtube_video_asset_resource_names`	No
`marketing_image_asset_resource_names`	Yes
`square_marketing_image_asset_resource_names`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so safety is covered. The description adds real behavioral context beyond that: asset groups and assets must be created in a single batch, assets must pre-exist, and an ENABLED group begins serving from the campaign budget immediately upon approval — a consequence an agent would otherwise miss.

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?

Well front-loaded with the core action, then a requirements block and a clean Args section. It is long, but for a 15-parameter batch tool each section is load-bearing; the Returns note mildly overlaps the output schema.

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

Completeness5/5

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

Given 15 parameters, 0% schema coverage and a true mutation with destructive semantics, the description supplies everything needed: ordering constraint, asset minimums, defaults, formatting rules, and the serving consequence of the status default.

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% across 15 params, so the description must carry the load and does: it explains each parameter's meaning, per-list minimums and maximums, the ENABLED/PAUSED distinction, customer_id formatting (numbers only, no hyphens), and the 15-character limit on path1/path2.

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?

States a specific verb and resource (creates an asset group for a Performance Max campaign) plus the linking behavior in the same sentence. An agent can distinguish it from create_performance_max_campaign and add_assets_to_asset_group without opening any schema.

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?

Gives explicit ordering guidance (create assets first with create_text_asset, create_image_asset, etc., then pass resource names) and the hard minimum/maximum asset counts. It does not explicitly point to add_assets_to_asset_group as the alternative for supplementing an existing group, which is the one obvious gap.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?