Skip to main content
Glama

google_ads_ads_update

Update the creative copy of a Responsive Search Ad by replacing headlines or descriptions while preserving omitted assets. Records before-state for rollback support.

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

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID to update.
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.
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.
Behavior5/5

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

With no annotations, the description fully discloses that the call replaces the ad under the same ID, resets learning, triggers re-review, and is not automatically reversible. It also explains side replacement semantics.

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?

Well-structured, front-loaded with purpose, then details, side effects, and alternatives. Every sentence earns its place; no wasted words.

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?

Covers all necessary context for a mutating tool: what it does, how it works, side effects, alternatives, and output (returns updated ad). No gaps given schema richness.

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%, baseline 3. The description reiterates that omission preserves the current side, but the schema already states 'Omit to keep the current headlines unchanged.' Minimal added value beyond schema.

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?

Clearly states the tool updates creative copy of an RSA by replacing headlines/descriptions. The verb 'updates' and resource 'Responsive Search Ad' are specific, and it distinguishes from sibling tools like 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?

Explicitly advises using google_ads_ads_update_status for status-only changes and suggests recording before-state for rollback. It explains when to omit sides to preserve them, providing clear context for use.

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