Reddit Ads MCP server

reddit get pixels

reddit_get_pixels

Read-onlyIdempotent

Lists Reddit ad pixels accessible to a specified ad account, with cursor pagination, to help identify tracking pixels for campaign setup.

Instructions

List pixels accessible to the allowed Reddit ad account.

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.
`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?

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds only the permission-scoping phrase 'accessible to the allowed Reddit ad account'; it does not add meaningful behavioral context beyond that, but it does not contradict the 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?

The description is a single front-loaded sentence with no filler. Every word contributes to stating the resource and scope.

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 simple paginated list endpoint, the structured fields are rich: annotations cover safety, the schema documents pagination, and an output schema exists. The description is sufficient, though it could briefly clarify that results are paginated.

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 explains adAccountId, limit, and cursor in detail. The description adds no parameter-level meaning beyond the schema, which is the baseline expectation at full coverage.

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 ('List pixels') plus scope ('accessible to the allowed Reddit ad account'). It is clear what the tool does, though it does not explicitly distinguish itself from any sibling tool.

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?

The description implies the tool is for listing pixels in an allowed ad account, but it gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer usage from the purpose sentence alone.

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