AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Update a responsive search ad

update_responsive_search_ad

Update an existing responsive search ad in place by changing final URLs, paths, headlines, or descriptions; preview changes before applying.

Instructions

Update mutable fields on an existing RSA in place — returns a PREVIEW.

Edits an existing RSA without creating a new ad; the ad keeps its ID. Google Ads API v23 (AdService.MutateAds) permits in-place mutation of final_urls, path1, path2, headlines, and descriptions. At least one mutation must be requested.

IMPORTANT: replacing headlines or descriptions is NOT a free in-place edit. Even though the ad ID is preserved, swapping the creative text RESETS the ad's asset-combination learning and performance history and sends the ad BACK THROUGH Google policy review — Google treats the creative as new for optimization. URL-only and path-only edits do not incur this. When headlines/descriptions change, the returned preview includes a warnings entry stating this trade-off before anything is applied.

Returns a preview with a plan_id; nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema

Name	Required	Description
`ad_id`	Yes	Numeric ID of the existing responsive search ad.
`path1`	No	Empty means no change; non-empty sets the first display path (max 15 chars).
`path2`	No	Empty means no change; non-empty sets the second display path (max 15 chars).
`final_url`	No	Empty means no change; non-empty replaces the final URL and is checked for reachability.
`headlines`	No	LIST-REPLACE: None or [] means no change; a non-empty list fully swaps in for the existing headlines. Google's RSA constraints apply: 3-15 headlines, max 30 chars each, every pin position fillable. Each entry is a plain string (unpinned) or {"text": "...", "pinned_field": "HEADLINE_1"} (HEADLINE_1-3). Insertion tags such as {KeyWord:Clogged Drain Service} count as their default text, which is required.
`clear_path1`	No	True sets path1 to an empty string (overrides path1).
`clear_path2`	No	True sets path2 to an empty string (overrides path2).
`customer_id`	No	Google Ads customer ID (digits, e.g. "1234567890"). Empty uses the configured default account.
`descriptions`	No	LIST-REPLACE: None or [] means no change; a non-empty list fully swaps in. 2-4 descriptions, max 90 chars each, pins to DESCRIPTION_1 or DESCRIPTION_2 with every position fillable. Same entry format and insertion-tag counting as headlines.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.32.0Oct 16, 2026

changedInput schema / properties / descriptions / description

Previous value: -"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in. 2-4 descriptions, max 90 chars each, at most 1 per\npin slot (DESCRIPTION_1, DESCRIPTION_2). Same entry format and\ninsertion-tag counting as headlines."New value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in. 2-4 descriptions, max 90 chars each, pins to\nDESCRIPTION_1 or DESCRIPTION_2 with every position fillable. Same\nentry format and insertion-tag counting as headlines."

changedInput schema / properties / headlines / description

Previous value: -"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in for the existing headlines. Google's RSA constraints\napply: 3-15 headlines, max 30 chars each, at most 2 per pin slot.\nEach entry is a plain string (unpinned) or {\"text\": \"...\",\n\"pinned_field\": \"HEADLINE_1\"} (HEADLINE_1-3). Insertion tags such as\n{KeyWord:Clogged Drain Service} count as their default text, which\nis required."New value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in for the existing headlines. Google's RSA constraints\napply: 3-15 headlines, max 30 chars each, every pin position fillable.\nEach entry is a plain string (unpinned) or {\"text\": \"...\",\n\"pinned_field\": \"HEADLINE_1\"} (HEADLINE_1-3). Insertion tags such as\n{KeyWord:Clogged Drain Service} count as their default text, which\nis required."

Changed2 schema fields changedv0.29.2Oct 15, 2026

changedInput schema / properties / descriptions / description

Previous value: -"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in. 2-4 descriptions, max 90 chars each, at most 1 per\npin slot (DESCRIPTION_1, DESCRIPTION_2). Same entry format as\nheadlines."New value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in. 2-4 descriptions, max 90 chars each, at most 1 per\npin slot (DESCRIPTION_1, DESCRIPTION_2). Same entry format and\ninsertion-tag counting as headlines."

changedInput schema / properties / headlines / description

Previous value: -"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in for the existing headlines. Google's RSA constraints\napply: 3-15 headlines, max 30 chars each, at most 2 per pin slot.\nEach entry is a plain string (unpinned) or {\"text\": \"...\",\n\"pinned_field\": \"HEADLINE_1\"} (HEADLINE_1-3)."New value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in for the existing headlines. Google's RSA constraints\napply: 3-15 headlines, max 30 chars each, at most 2 per pin slot.\nEach entry is a plain string (unpinned) or {\"text\": \"...\",\n\"pinned_field\": \"HEADLINE_1\"} (HEADLINE_1-3). Insertion tags such as\n{KeyWord:Clogged Drain Service} count as their default text, which\nis required."

Changed9 schema fields changedv0.27.1Oct 14, 2026

addedInput schema / properties / ad_id / description

Added value: +"Numeric ID of the existing responsive search ad."

addedInput schema / properties / clear_path1 / description

Added value: +"True sets path1 to an empty string (overrides path1)."

addedInput schema / properties / clear_path2 / description

Added value: +"True sets path2 to an empty string (overrides path2)."

addedInput schema / properties / customer_id / description

Added value: +"Google Ads customer ID (digits, e.g. \"1234567890\"). Empty\nuses the configured default account."

addedInput schema / properties / descriptions / description

Added value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in. 2-4 descriptions, max 90 chars each, at most 1 per\npin slot (DESCRIPTION_1, DESCRIPTION_2). Same entry format as\nheadlines."

addedInput schema / properties / final_url / description

Added value: +"Empty means no change; non-empty replaces the final URL and\nis checked for reachability."

addedInput schema / properties / headlines / description

Added value: +"LIST-REPLACE: None or [] means no change; a non-empty list\nfully swaps in for the existing headlines. Google's RSA constraints\napply: 3-15 headlines, max 30 chars each, at most 2 per pin slot.\nEach entry is a plain string (unpinned) or {\"text\": \"...\",\n\"pinned_field\": \"HEADLINE_1\"} (HEADLINE_1-3)."

addedInput schema / properties / path1 / description

Added value: +"Empty means no change; non-empty sets the first display path\n(max 15 chars)."

addedInput schema / properties / path2 / description

Added value: +"Empty means no change; non-empty sets the second display path\n(max 15 chars)."

Addedv0.13.3Sep 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: despite destructiveHint=false, it discloses that swapping headlines/descriptions resets asset-combination learning and sends the ad back through policy review, while URL/path edits do not — a critical side effect the annotations do not convey. It also explains the preview-with-plan_id staging semantics and the returned warnings entry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the in-place edit plus return type, then trade-offs under an IMPORTANT marker, then the confirm flow. Slightly repetitive (the preview is stated at the top and again at the end) and the trailing API doc URL adds little, but the structure is easy to scan.

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?

With an output schema present, the description needn't document return values, and it correctly focuses on the mutation constraints, side effects, and staging flow instead. Annotations cover safety, schema covers parameters; nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema carries the field semantics (baseline 3). The description adds a genuine cross-parameter constraint the schema cannot express — at least one mutation must be requested — and corroborates which fields are in-place mutable (final_urls, path1, path2, headlines, descriptions).

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?

Opens with a specific verb+resource (update mutable fields on an existing RSA) and distinguishes itself from the create path by stating 'without creating a new ad; the ad keeps its ID.' The scope is further pinned by naming the exact mutable fields, so an agent can separate this from draft_responsive_search_ad without opening either schema.

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?

Gives clear conditions of use: 'At least one mutation must be requested,' which fields are permitted, and the required preview-then-confirm_and_apply workflow. It doesn't explicitly name a sibling alternative for the create case, but the when/why is unambiguous for 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