Reddit Ads MCP server

reddit get custom audience

reddit_get_custom_audience

Read-onlyIdempotent

Read a Reddit custom audience and verify it belongs to the specified ad account before using it for targeting or campaign work.

Instructions

Read one Reddit custom audience and verify that it belongs to the ad account.

Input Schema

Name	Required	Description	Default
`id`	Yes	ID of the Reddit custom audience to read. It must belong to adAccountId.
`adAccountId`	Yes	Reddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds the meaningful constraint that the audience must belong to the ad account, but it does not describe error behavior, auth requirements, or rate limits.

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

Conciseness5/5

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

The description is a single efficient sentence with no filler. The core action and the ownership constraint are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the annotations carry the safety profile, so the description need not explain return values. It is nearly complete for a two-parameter read tool, though it omits what happens when the audience is not found or does not belong to the ad account.

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%, with rich field descriptions for both id and adAccountId, including the ID pattern and ad account format. The description reinforces the ownership relationship between id and adAccountId 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: read one Reddit custom audience, plus an ownership verification requirement. The singular 'one' implicitly distinguishes it from the sibling list tool reddit_get_custom_audiences, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied for fetching a single custom audience by ID and confirming it belongs to the ad account. It does not state when to use this versus reddit_get_custom_audiences or reddit_get_saved_audience, nor does it mention exclusions or prerequisites.

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