Skip to main content
Glama

google_ads_ads_update

Replace headlines and descriptions of an existing Responsive Search Ad in Google Ads. Returns the updated ad. Resets learning and triggers re-review. For status-only changes, use the dedicated status update tool.

Instructions

Updates the creative copy of an existing Responsive Search Ad by replacing headlines and/or 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, reversible via rollback_apply. 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
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.
ad_group_idYesParent ad group ID.
ad_idYesAd ID to update.
headlinesNoReplacement headlines (3 to 15). Each max 30 characters display width.
descriptionsNoReplacement descriptions (2 to 4). Each max 90 characters display width.
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses that the ad is replaced under the same ID, resetting learning and triggering re-review. Also notes mutability and reversibility.

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?

Two well-structured sentences with essential information front-loaded. Every sentence adds value without redundancy.

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?

Completely covers purpose, side effects, usage guidance, and return value. No gaps given schema coverage and absence of output schema.

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% with descriptions for all parameters. The description adds no new parameter-level info beyond what the schema already states.

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 existing Responsive Search Ad by replacing headlines/descriptions. Distinguishes from sibling tool for status updates.

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 notes when to use (editing creative copy) and when not (use status update for pause/resume). Mentions replacement behavior, learning reset, re-review, and reversibility via rollback_apply.

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