Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

Draft Performance Max asset changes

draft_asset_group_assets

Draft additions or removals of Performance Max asset group assets, returning a preview with asset counts before any change is confirmed and applied.

Instructions

Draft adding and/or removing assets of a Performance Max asset group — returns a PREVIEW.

Adds new text, image and YouTube assets and unlinks existing ones in one atomic request, so an asset is replaced without the group dropping below Google's minimums (3 headlines, 1 long headline, 2 descriptions, one of them at most 60 characters). Texts already in the group are skipped. Images are checked and sorted by aspect ratio; removed assets stay in the account's asset library. The preview lists the asset counts per type after the change. Nothing changes until confirm_and_apply applies the plan_id; a dry run has Google validate it.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNoImages to add, each {"url": "..."} or {"upload_id": "up_..."} with an optional "role": "marketing" (default; landscape 1.91:1, square 1:1 or portrait 4:5 by aspect ratio), "logo" (1:1) or "landscape_logo" (4:1). PNG, JPEG or GIF up to 5120 KB.
headlinesNoHeadlines to add, at most 30 characters each (up to 15 in the group).
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
descriptionsNoDescriptions to add, at most 90 characters (up to 5).
business_nameNoBusiness name to add, at most 25 characters (one per group).
asset_group_idYesNumeric asset group id (from get_pmax_performance or get_pmax_assets).
long_headlinesNoLong headlines to add, at most 90 characters (up to 5).
remove_asset_idsNoAsset ids to unlink from the group (from get_pmax_assets).
youtube_video_idsNoYouTube video ids to add (the 11 characters after "v=" in the URL), up to 5 per group.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.27.1

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 (which only cover readOnly=false, destructive=false, openWorld=true). It discloses atomicity, Google minimums that must be preserved, that already-present texts are skipped, aspect-ratio sorting of images, that removed assets remain in the library, that the preview lists per-type counts, and that nothing mutates until confirm_and_apply.

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 action and the PREVIEW outcome, then dense but useful constraint detail. Every sentence carries information; slightly long but no filler.

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 9-parameter mutation-drafting tool with an output schema covering the preview, the description supplies the workflow, constraints, and side-effect profile an agent needs. Nothing essential is missing.

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 coverage is 100%, so baseline is 3, but the description adds constraint semantics not in the schema: the group minimums (3 headlines, 1 long headline, 2 descriptions, one within 60 chars) and image role/aspect-ratio handling. This meaningfully enriches parameter understanding.

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?

States a specific verb (draft adding/removing) plus resource (Performance Max asset group assets) and immediately flags the PREVIEW nature. An agent can distinguish it from siblings like draft_image_assets or draft_asset_group_signals without opening any 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?

Explicitly routes the agent to confirm_and_apply for actually applying the plan_id, establishing the two-step draft/apply workflow. The 'one atomic request' framing also signals when to prefer this over piecemeal single-asset tools, though no explicit when-not or exclusion is stated.

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