Skip to main content
Glama

google_ads_asset_group_images_replace

Replace a Performance Max asset group image or logo in one atomic mutation, preventing minimum-asset errors. Use an existing image asset or upload a local file; dimensions are checked before change.

Instructions

Swaps one image or logo of a Performance Max asset group for another. Mutating. Use this whichever situation you are in: pass new_asset_id when the account already holds the image (google_ads_image_assets_list finds one), or new_image_path to upload a local file first — exactly one of the two, and mureo handles the difference. The replacement is linked under the same field_type and the old link is removed in ONE atomic GoogleAdsService.mutate, so the asset group's asset count for that field type never dips below the Performance Max minimum (a removal issued on its own is refused with AssetGroupError.NOT_ENOUGH_MARKETING_IMAGE_ASSET or its square / logo twin). Neither Asset is deleted; only the old link to this asset group is. Google enforces a shape per slot — MARKETING_IMAGE 1.91:1 (min 600x314), SQUARE_MARKETING_IMAGE 1:1 (min 300x300), PORTRAIT_MARKETING_IMAGE 4:5 (min 480x600), LOGO 1:1 (min 128x128), LANDSCAPE_LOGO 4:1 (min 512x128) — and mureo checks it before uploading or linking anything, then refuses with the rule spelled out. It never crops or resizes. Returns {asset_group_id, field_type, added: {asset_id, asset_name, width_pixels, height_pixels, source ('existing_asset' | 'uploaded'), asset_group_asset}, removed: {asset_id, asset_name, url, asset_group_asset}, note}. Not automatically reversible — to swap back, call this tool again with the old asset_id; record before-state with mureo_state_action_log_append if you may need to roll back. Call google_ads_asset_group_assets_list first to get old_asset_id. For headlines and descriptions use google_ads_asset_group_assets_replace instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_typeYesWhich image slot to swap. Must match the field_type the old asset is linked under — the same image can be linked as more than one field type, and each has its own required aspect ratio.
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.
new_asset_idNoAn image asset the account already holds, from google_ads_image_assets_list or from another asset group's entry. Rejected if it is not an image asset, if its dimensions do not fit this field_type, or if it is already linked to this asset group under this field_type (Google Ads refuses a duplicate link). Supply this OR new_image_path, never both.
old_asset_idYesasset_id of the entry being replaced, from google_ads_asset_group_assets_list. Rejected before any write if it is not linked to this asset group under this field_type.
asset_group_idYesAsset group whose image is being changed, as reported by google_ads_asset_group_assets_list.
new_image_nameNoAsset name for the uploaded image. Only used with new_image_path; defaults to the file name.
new_image_pathNoLocal path to an image to upload and link (jpg/jpeg/png/gif, max 5MB). Its dimensions are checked against this field_type BEFORE the upload, so a wrongly proportioned file costs no API call. Supply this OR new_asset_id, never both.

Schema Changelog

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

  1. Addedv0.13.1

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels. It discloses that the operation is mutating, atomic ('in ONE atomic GoogleAdsService.mutate'), does not delete assets, enforces shape constraints with specific dimensions, and is not automatically reversible. It even explains the error case with NOT_ENOUGH_MARKETING_IMAGE_ASSET and notes it never crops or resizes.

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 every sentence adds value: it fronts the purpose, then logically flows through usage, atomicity, asset shape rules, return value, rollback caveat, and alternatives. There is no filler or repetition; it is densely informative without being bloated.

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 the tool's complexity (7 parameters, no output schema, mutating behavior), the description is exceptionally complete. It details return structure, error behavior, prerequisites, shape enforcement, and rollback recommendations. It covers all aspects an agent needs to invoke the tool correctly and interpret results.

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?

Although schema coverage is 100%, the description adds significant semantics beyond the schema: it clarifies the mutual exclusivity of new_asset_id and new_image_path, explains rejection conditions ('Rejected if it is not an image asset, if its dimensions do not fit this field_type, or if it is already linked'), and specifies dimension checks before upload. This goes well beyond the schema's raw definitions.

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 clear, specific verb-resource pairing: 'Swaps one image or logo of a Performance Max asset group for another.' It distinguishes itself from the sibling tool google_ads_asset_group_assets_replace by explicitly stating 'For headlines and descriptions use google_ads_asset_group_assets_replace instead.' This fully differentiates the purpose.

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?

It provides explicit when-to-use guidance: 'Use this whichever situation you are in: pass new_asset_id when the account already holds the image... or new_image_path to upload a local file first' and mandates a prerequisite: 'Call google_ads_asset_group_assets_list first to get old_asset_id.' It also states when not to use (for headlines/descriptions) and references rollback via mureo_state_action_log_append.

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