Skip to main content
Glama

google_ads_asset_group_assets_list

List text and image creative assets per Performance Max asset group. Returns headlines, descriptions, image URLs, and link status to pinpoint which asset group serves each asset.

Instructions

Lists the text AND the images attached to Performance Max asset groups. Read-only. This is the tool for P-MAX creative: google_ads_ads_list returns no rows for a Performance Max campaign because P-MAX has no ad_group_ad — its headlines and its pictures alike live on asset_group_asset. It is also the only way to say WHICH asset group serves a given image; google_ads_image_assets_list is account-wide and does not. Returns one entry per link. Every entry carries {resource_name (the asset_group_asset handle), field_type, status (the LINK status: 'ENABLED' | 'PAUSED' | 'REMOVED'), asset_id, asset_group_id, asset_group_name, campaign_id, campaign_resource_name}. field_type says what the rest of the entry holds: a text link ('HEADLINE' | 'LONG_HEADLINE' | 'DESCRIPTION') adds {text}; an image link ('MARKETING_IMAGE' | 'SQUARE_MARKETING_IMAGE' | 'PORTRAIT_MARKETING_IMAGE' | 'LOGO' | 'LANDSCAPE_LOGO') adds {asset_name, url (the full-size serving URL — fetch it to actually look at the creative), width_pixels, height_pixels}. Entries are returned in the order the API returned them and are not deduplicated — two links carrying the same asset are two entries, because that is what the asset group has. Video, business name and other field types are not returned. Pass the asset_id of the entry you want to change to google_ads_asset_group_assets_replace (text) or google_ads_asset_group_images_replace (images).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idNoRestrict to the asset groups of one Performance Max campaign. Use this when you have a campaign id but not an asset group id.
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
asset_group_idNoRestrict to one asset group. Omit to list every Performance Max asset group in the account (or in campaign_id, when that is given).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.13.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries behavioral disclosure. It clearly states read-only behavior, per-link entry semantics, lack of deduplication, API ordering, which field types are omitted, and the meaning of link status values. This is exemplary transparency for a list tool.

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 long but densely informative; every sentence provides distinct value including return fields, conditional payloads, deduplication behavior, exclusions, and sibling tool references. It is front-loaded with the core purpose and then systematically adds necessary detail.

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 tool with no output schema, the description compensates by fully enumerating returned fields, conditional fields based on field_type, screenshot URL semantics, ordering, deduplication, omissions, and related write tools. The parameter guidance and alternative tool comparisons make it contextually complete.

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 coverage is 100%, so parameters are already fully documented in the input schema. The description adds filter-related context (restrict by campaign or asset group) but does not need to repeat the schema details. Baseline 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?

The description opens with a precise verb and resource: "Lists the text AND the images attached to Performance Max asset groups." It further distinguishes itself from sibling tools by explaining that google_ads_ads_list returns no rows for P-MAX and that this tool uniquely identifies which asset group serves a given image.

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

Usage Guidelines5/5

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

Usage context is explicitly stated: it is the tool for P-MAX creative, with direct exclusions for google_ads_ads_list and google_ads_image_assets_list. It also gives forward guidance, telling users to pass asset_id to the replacement tools for modifications.

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/logly/mureo'

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