AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Draft a Reddit retargeting audience

draft_reddit_custom_audience

Draft a Reddit retargeting audience from website pixel events or campaign engagement without uploading personal data, preview it, then apply it to target or exclude in ad groups.

Instructions

Draft a Reddit retargeting audience (website visitors or engaged people) — PREVIEW.

Builds the audience from data Reddit already has: people the pixel saw on the website, or people who saw or engaged with the account's campaigns. No personal data is uploaded. Nothing changes until confirm_and_apply applies the plan_id; Reddit then fills the audience (status PENDING, up to a day), and an ad group uses it through update_reddit_ad_group custom_audience_ids (target) or excluded_custom_audience_ids (exclude).

Reddit Ads API: https://ads-api.reddit.com/docs/v3/

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Audience name, 3 to 500 characters.
`events`	No	Website audiences: the pixel events that qualify, any of PAGE_VISIT (default), VIEW_CONTENT, SEARCH, ADD_TO_CART, ADD_TO_WISHLIST, PURCHASE, LEAD, SIGN_UP, CUSTOM.
`pixel_id`	No	Pixel to build a website audience from (get_reddit_pixels).
`engagements`	No	Engagement audiences: what people did, any of CLICKS (default), IMPRESSIONS, UPVOTES, COMMENT_SUBMISSIONS, VIDEO_STARTED, VIDEO_WATCHED_50_PERCENT, VIDEO_WATCHED_100_PERCENT.
`campaign_ids`	No	Engagement audiences: the campaigns whose audience to reuse (get_reddit_campaigns).
`ad_account_id`	No	Reddit ad account id (from list_reddit_accounts). Empty uses reddit.ad_account_id from the config.
`audience_type`	Yes	PIXEL_RETARGETING (website visitors, from the pixel) or ENGAGEMENT_RETARGETING (people who saw or engaged with campaigns).
`custom_events`	No	Website audiences: custom pixel event names to include (adds CUSTOM to events), at most 50.
`lookback_window_days`	No	How far back an action counts: 1 to 90 days for website audiences (default 30), 1 to 180 for engagement audiences (default 90).

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.4/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=true) by disclosing that nothing is mutated until confirm_and_apply, that Reddit then asynchronously fills the audience (status PENDING, up to a day), and that no personal data is uploaded. These are exactly the operational facts an agent needs for a preview tool.

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-loads the essential fact (PREVIEW) and orders the rest as source -> safety -> lifecycle. Every sentence carries information, though the doc link and some phrasing are marginally verbose.

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, return values need no explanation, and the description still covers the full lifecycle (draft -> confirm -> PENDING fill -> ad-group usage). Nothing critical is missing for correct invocation.

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 the schema already documents all nine parameters including the two audience_type values and get_reddit_pixels/get_reddit_campaigns sourcing hints. The description reinforces the website-vs-engagement split but adds no syntax or format detail beyond the schema.

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) plus resource (Reddit retargeting audience) and immediately scopes it to the two audience kinds: website visitors and engaged people. An agent can tell it apart from sibling `draft_audience_attachment` or `search_audience_segments` without reading the 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?

Explains the workflow context clearly: it only produces a preview, nothing changes until `confirm_and_apply` applies the plan_id, and the result is consumed via `update_reddit_ad_group` custom_audience_ids/excluded_custom_audience_ids. It names the relevant downstream tools but does not explicitly contrast with alternative audience-creation paths.

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

Deploy Server