Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_asset_group_assets_replace

Replace a Google Ads Performance Max asset group's headline, long headline, or description with new text in one atomic operation, preserving the required asset count minimum.

Instructions

Swaps one headline, long headline or description of a Performance Max asset group for new text. Mutating. A Google Ads text Asset is immutable, so this creates a new Asset, links it to the asset group under the same field_type, and removes the old link — all three 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_*). The old Asset itself is not deleted; only its link to this asset group is. Returns {asset_group_id, field_type, added: {asset_id, asset_resource_name, text, asset_group_asset}, removed: {asset_id, text, asset_group_asset}, note}. Not automatically reversible — to swap back, call this tool again with the old text; 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
new_textYesReplacement copy. Display-width limits (a full-width character counts as two): HEADLINE 30, LONG_HEADLINE 90, DESCRIPTION 90. Text already linked under the same field_type is rejected — Google Ads refuses a duplicate link.
field_typeYesWhich slot to swap. Must match the field_type the old asset is linked under — the same text asset can be linked as more than one field type.
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.
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 copy is being changed, as reported by google_ads_asset_group_assets_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Addedv0.13.1

TDQS

A4.5/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 behavioral burden and does so thoroughly. It discloses that the tool mutates, creates a new Asset, links it, removes the old link, performs all steps in one atomic mutate, does not delete the old Asset, and is not automatically reversible. This is strong transparency beyond anything structured fields provide.

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 dense but every sentence earns its place: purpose, mutation warning, atomicity rationale, non-deletion of old asset, return shape, rollback caveat, and prerequisite call. It is front-loaded with the core purpose and then layers the necessary operational details without fluff.

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 mutating tool with no output schema and no annotations, the description is remarkably complete. It covers side effects, atomicity, failure conditions, return values, rollback, and the prerequisite list call, leaving little ambiguity about how an agent should invoke it correctly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents each parameter in detail. The tool description adds some contextual value by telling the agent where old_asset_id comes from and what the returned shapes are, but it does not need to compensate for missing schema information.

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 specific verb and resource: 'Swaps one headline, long headline or description of a Performance Max asset group for new text.' It clearly names the operation, the object being modified, and the asset types involved, and it is easy to distinguish from siblings like google_ads_asset_group_images_replace.

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 clear prerequisites ('Call google_ads_asset_group_assets_list first to get old_asset_id') and rollback guidance ('record before-state with mureo_state_action_log_append'). It explains why this atomic swap should be used instead of a standalone removal, but it does not explicitly name alternatives or state when not to use this tool.

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

Deploy Server

Other Tools