AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Draft audience attachment

draft_audience_attachment

Preview attaching audiences to a Google Ads campaign or ad group as observation, targeting, or exclusion before applying changes.

Instructions

Draft attaching audiences to a campaign or ad group as observation, targeting or exclusion: returns a PREVIEW.

Observation (the default) keeps the reach: the audiences adjust bids and show up in reports. Targeting narrows delivery to the audiences and needs a double confirmation. Exclusions keep the people out and leave the mode alone. The draft refuses combinations Google does not allow (custom segments on Search, combined segments outside Search, audiences at both campaign and ad group level) and lists that cannot serve; Performance Max is refused with a pointer to draft_asset_group_signals. 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
`mode`	No	"observation" (default) or "targeting". Ignored for exclusions.	observation
`exclude`	No	True to exclude the audiences instead of adding them.
`ad_group_id`	No	Numeric ad group id. Pass this or campaign_id.
`campaign_id`	No	Numeric campaign id. Pass this or ad_group_id.
`customer_id`	No	Google Ads customer ID (digits, dashes optional). Defaults to the configured account.
`segment_ids`	No	In-market or affinity segments (segment_id from search_audience_segments).
`user_list_ids`	No	Remarketing or customer lists (user_list_id from get_audience_lists).
`custom_audience_ids`	No	Custom segments (custom_audience_id from get_audience_lists); Display and Video only.
`combined_audience_ids`	No	Combined segments (combined_audience_id from get_audience_lists); Search only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.29.2Oct 15, 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 (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that it returns only a PREVIEW, that nothing changes until confirm_and_apply applies the plan_id, that a dry run has Google validate it, and that specific Google-invalid combinations are refused. This is exactly the behavioral context an agent needs before invoking.

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?

The purpose and preview/draft semantics are front-loaded in the first sentence, and the rest is organized by mode and validation rule. It is dense but every clause carries meaning, though it could be tightened slightly.

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 and annotations covering the safety profile, the description fills the remaining gaps: the draft/confirm lifecycle, mode semantics, and validation refusals. Nothing essential to correct invocation is missing.

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 description coverage is 100%, so all nine parameters are already documented in the schema. The description reinforces the mode/exclude interaction but adds little syntax or format detail beyond what the schema already provides; baseline 3 is appropriate.

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?

The opening sentence states a specific verb (draft attaching audiences), the resource (audiences), and the target scope (campaign or ad group), plus the three modes. It clearly distinguishes itself from the apply-oriented sibling confirm_and_apply and from draft_asset_group_signals.

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 explains when each mode applies (observation default, targeting narrows delivery and needs double confirmation, exclusions leave mode alone) and when the tool is the wrong choice (Performance Max is refused with a pointer to draft_asset_group_signals). It also clarifies the draft-then-confirm workflow that gates all changes.

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

Deploy Server