Skip to main content
Glama
get-mcp-ads

Reddit Ads MCP server

reddit get saved audience

reddit_get_saved_audience
Read-onlyIdempotent

Retrieve a Reddit saved audience by ID and confirm it belongs to the specified ad account before using it in campaign or targeting workflows.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesID of the Reddit saved audience to read. It must belong to adAccountId.
adAccountIdYesReddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds one useful behavioral note - that it verifies ownership by adAccountId - but does not say what happens on a mismatch (error vs empty). Given annotation coverage, a 3 is appropriate.

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?

A single tight sentence with the core action front-loaded and no filler. Every clause earns its place.

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?

With 2 required params, full schema coverage, an output schema, and complete annotations, the description supplies what's needed to call it correctly. The only minor gap is not describing the ownership-verification failure behavior.

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 coverage is 100%, so both parameters (id, adAccountId) are fully documented in the schema itself, including the a2_... format note. The description adds no parameter detail beyond the schema, so the baseline 3 applies.

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 ('one Reddit saved audience'), scoped to exactly one item, which implicitly distinguishes it from the plural reddit_get_saved_audiences sibling. It does not explicitly name that sibling, but the singular scope makes the distinction inferable.

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 (fetch a single saved audience by id within an ad account) but there is no explicit when-to-use, when-not-to-use, or named alternative such as the list tool or the custom-audience tools. An agent must infer the context.

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