Reddit Ads MCP server

reddit get targeting

reddit_get_targeting

Read-onlyIdempotent

Read an ad group's actual targeting configuration, including inclusions, exclusions, geo, age/gender, languages, interests, communities, keywords, devices, and audience IDs—not delivery demographics.

Instructions

Read actual ad-group targeting: inclusions, exclusions, geo, age/gender, languages, interests, communities, keywords, devices and audience IDs. This is configuration, not delivery demographics.

Input Schema

Name	Required	Description	Default
`adGroupId`	Yes	Ad group ID whose targeting 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

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds valuable context that the output is configuration (not delivery data) and enumerates the targeting components, which helps the agent interpret results. No auth or rate-limit details, but those are not expected given annotations.

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?

Two sentences, front-loaded with the main purpose and a concise clarification. Every sentence earns its place with no redundancy.

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?

An output schema exists, so return values need not be explained. Annotations cover safety and idempotency. The description enumerates targeting fields and clarifies the data type (configuration vs. delivery), making the definition complete 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%, and both parameters (adAccountId, adGroupId) are fully documented in the schema. The description does not add any meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb ('Read') and resource ('actual ad-group targeting') and enumerates the targeting fields. It distinguishes configuration from delivery demographics, but does not explicitly name the sibling tool reddit_get_targeting_options, leaving some inference to the agent.

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?

Provides clear context: use to read actual targeting configuration, not delivery demographics. The contrast with 'delivery demographics' serves as an exclusion, but no explicit alternative tool or when-not-to-use condition is given.

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