Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_update

Replace an existing Responsive Search Ad's headlines and/or descriptions while preserving the omitted side; use for creative copy changes, and use a status tool for pause/resume.

Instructions

Updates the creative copy of an existing Responsive Search Ad by replacing headlines and/or descriptions. A supplied side is fully replaced (Google has no per-asset patch); omit a side to leave it unchanged — the omitted side is read from the current ad and preserved, so updating headlines never wipes descriptions. Returns the updated ad. Google Ads does not support in-place edit of RSA creative assets — this call typically replaces the ad with a new one under the same ID, which resets learning and triggers re-review. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. For status-only changes (pause/resume) use google_ads_ads_update_status, which is lighter-weight and does not reset learning.

Input Schema

NameRequiredDescriptionDefault
ad_idYesAd ID to update.
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.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
headlinesNoReplacement headlines (3 to 15) — the full new set, since the supplied side is replaced wholesale. Omit to keep the current headlines unchanged. Each max 30 characters display width.
ad_group_idYesParent ad 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.
decision_idNoA proposed decision this change carries out.
descriptionsNoReplacement descriptions (2 to 4) — the full new set, since the supplied side is replaced wholesale. Omit to keep the current descriptions unchanged. Each max 90 characters display width.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. 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"
+}
  5. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  6. Addedv0.10.11
  7. Removedv0.10.9
  8. Changed2 schema fields changedv0.10.7
    • changedInput schema / properties / descriptions / description
      Previous value: -"Replacement descriptions (2 to 4). Each max 90 characters display width."New value: +"Replacement descriptions (2 to 4) — the full new set, since the supplied side is replaced wholesale. Omit to keep the current descriptions unchanged. Each max 90 characters display width."
    • changedInput schema / properties / headlines / description
      Previous value: -"Replacement headlines (3 to 15). Each max 30 characters display width."New value: +"Replacement headlines (3 to 15) — the full new set, since the supplied side is replaced wholesale. Omit to keep the current headlines unchanged. Each max 30 characters display width."
  9. Addedv0.9.12
  10. Removedv0.9.6
  11. Addedv0.9.2
  12. Removedv0.9.1
  13. Addedv1.0.5

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 carries the full behavioral burden and does so well: it discloses that Google has no per-asset patch, that the ad is typically replaced under the same ID, that learning resets and re-review is triggered, that the mutation is not automatically reversible, and that the before-state should be recorded via mureo_state_action_log_append.

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 front-loaded with purpose and replacement semantics, then moves through return behavior, side effects, reversibility, and the status-tool alternative. Every sentence adds useful information for a mutation tool with no annotations.

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 lack of annotations and no output schema, the description is complete enough for an agent to call this safety-critical mutation correctly. It covers what changes, how omitted sides are preserved, what is returned, the operational side effects, and the rollback/logging path.

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 schema already documents the parameters, including the full-set replacement semantics for headlines and descriptions. The description reinforces that replacement model but does not add substantial parameter-level meaning beyond what the schema already provides for reason, expected, approval, decision_id, customer_id, or the asset arrays.

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 gives a specific verb and resource: it updates the creative copy of an existing Responsive Search Ad by replacing headlines and/or descriptions. It also distinguishes this creative-asset update from the lighter status-only operation on the sibling tool google_ads_ads_update_status.

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 explicitly explains when to use this tool versus the status sibling tool: use this for creative-copy replacement, and use google_ads_ads_update_status for pause/resume because that path does not reset learning. It also clarifies the replace-wholesale versus omit-to-preserve behavior.

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