Skip to main content
Glama
Sign In

AdCopilot

by cloud.adcopilot.mcp
OverviewDiscussionsAdmin

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: d80f65c0.

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_id": "<campaign_id>",
      "name": "<name>",
      "final_url": "<final_url>",
      "headline_asset_resource_names": "<headline_asset_resource_names>",
      "description_asset_resource_names": "<description_asset_resource_names>",
      "long_headline_asset_resource_names": "<long_headline_asset_resource_names>",
      "marketing_image_asset_resource_names": "<marketing_image_asset_resource_names>",
      "square_marketing_image_asset_resource_names": "<square_marketing_image_asset_resource_names>"
    },
    "name": "create_asset_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
path1No
path2No
statusNoENABLED
final_urlYes
campaign_idYes
customer_idYes
final_mobile_urlNo
logo_asset_resource_namesNo
headline_asset_resource_namesYes
description_asset_resource_namesYes
long_headline_asset_resource_namesYes
youtube_video_asset_resource_namesNo
marketing_image_asset_resource_namesYes
square_marketing_image_asset_resource_namesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description adds substantive behavior on top: the single-batch constraint tying asset creation to group creation, the minimum asset composition required for Performance Max to accept the group, and the real-world cost implication of defaulting to ENABLED. It also states the shape of the response (resource name and linked asset count).

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?

It is front-loaded with purpose and ordering before the asset checklist and the Args block, and given 15 parameters almost every line carries new information. The min/max asset requirements appear once as bullets and are partly restated in the Args entries, which is mild redundancy but aids scanning.

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?

For a 15-parameter write tool with an output schema and full annotations, nothing material is missing: prerequisites, batch constraint, asset minimums, status semantics and URL path limits are all covered. Return values are summarized and backed by the output schema, so the description does not need to expand them further.

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 parameters, so the description must carry the load and does: it documents every argument including the no-hyphens rule for customer_id, per-parameter minimums and maximums (3-15 headlines, 2-5 descriptions, 1-5 long headlines), image orientation and recommended dimensions, the 15-character limit on path1/path2, and the ENABLED/PAUSED values that the schema does not encode as an enum.

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 first sentence names a specific verb and resource ("Creates an asset group for a Performance Max campaign") and adds the scoping behavior that assets are linked in the same call. It also distinguishes itself from the asset-creation siblings by naming create_text_asset and create_image_asset as prerequisites rather than alternatives.

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 a clear operating procedure: create assets first with the create_*_asset tools, then pass resource names here, and it explains the ENABLED-vs-PAUSED choice including the consequence that an ENABLED group serves from the campaign budget immediately. It stops short of routing to the obvious sibling add_assets_to_asset_group for later additions, which is the one alternative an agent would want.

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

All AdCopilot toolsInspect
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