AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Draft Performance Max product exclusions

draft_pmax_product_exclusions

Draft product exclusions for a Performance Max asset group by item ID, brand, or custom label. Preview the full exclusion list before applying changes.

Instructions

Draft which products a retail Performance Max asset group excludes — returns a PREVIEW.

Sets the full list of excluded values on one product dimension (item id, brand or a custom label); everything else stays included. Pass the complete list each time: values left out are included again, and an empty list includes all products. Works on asset groups that advertise all products or are already split on that one dimension; more complex product filters are refused and stay a job for Google Ads. The filter is rebuilt in one atomic request. 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

Name	Required	Description	Default
`dimension`	No	"item_id" (default), "brand", or "custom_label_0" to "custom_label_4".	item_id
`customer_id`	No	Google Ads customer ID (digits, dashes optional). Defaults to the configured account.
`asset_group_id`	Yes	Numeric asset group id of a Performance Max campaign with a Merchant Center feed (from get_pmax_performance).
`exclude_values`	Yes	Every value to exclude, e.g. item ids from the feed, brand names or custom label values. [] removes all exclusions.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.27.1Oct 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), which only say the call is non-destructive and touches an open system. The description discloses the replace-not-merge semantics ('Pass the complete list each time: values left out are included again'), the empty-list behavior, the single-dimension atomic rebuild, and that Google-side validation occurs on the dry run.

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 preview nature of the call, then organized into scope, semantics, and the confirm step. Efficient overall, though 'a dry run has Google validate it' and the PREVIEW warning overlap slightly in intent.

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 full schema coverage, an output schema present, and annotations covering the safety profile, the description still supplies the pieces an agent needs: preview-vs-apply workflow, list replacement semantics, dimension constraints, and the confirm_and_apply handoff. Nothing material 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 the baseline is 3, but the description adds real meaning: exclude_values is a full replacement list rather than an incremental addition, and dimension is constrained to one allowed dimension at a time. It doesn't restate enum-like details that the schema already carries, but the replacement semantics are genuinely additive.

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) and resource (Performance Max asset group product exclusions) and immediately flags that it produces a PREVIEW, not an applied change. This distinguishes it from sibling draft_* tools and especially from confirm_and_apply, which the description names explicitly.

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 bounds applicability: works on asset groups that advertise all products or are already split on that one dimension, while more complex product filters are refused. It also states the prerequisite for effect ('Nothing changes until confirm_and_apply applies the plan_id') and that a dry run has Google validate it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server