Reddit Ads MCP server

reddit get posts

reddit_get_posts

Read-onlyIdempotent

Lists advertising structured posts for a Reddit profile attached to an ad account and returns native image, video, carousel, or text configuration for campaign review and setup.

Instructions

List advertising structured posts for a profile attached to this account. Returns native image/video/carousel/text configuration.

Input Schema

Name	Required	Description
`limit`	No	Items per page, 1 to 100. Defaults to 50.
`cursor`	No	Opaque next_cursor returned by the previous page. Omit it for the first page.
`profileId`	Yes	Reddit profile ID (t2_...) attached to adAccountId. List them with reddit_get_profiles.
`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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds that posts carry native image/video/carousel/text configurations, but with an output schema present that return-shape detail is largely redundant and no pagination or scoping behavior beyond the profile link is disclosed.

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 short sentences with the core scope (posts for a profile) front-loaded and no filler. Nothing is wasted or buried.

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?

For a read-only paginated list tool with full schema coverage and an output schema, the description covers the essential scope. It could be stronger by naming the sibling that fetches a single post, but nothing needed to invoke it correctly 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%, with adAccountId, profileId, limit, and cursor all documented in the schema itself, including cross-references to reddit_get_profiles. The description adds no parameter-level meaning, so 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 ('List') and resource ('advertising structured posts') scoped to a profile, so the agent knows what entity is being enumerated. It does not distinguish itself from the sibling reddit_get_post (singular), which is the most likely source of confusion among 30+ siblings.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus reddit_get_post, reddit_list_ad_creatives, or reddit_get_creative_assets. The only implied guidance comes from the resource name itself; no exclusions, prerequisites, or alternative routing are given.

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