Skip to main content
Glama

Reddit ads

get_reddit_ads
Read-only

List Reddit ads with status, rejection_reason, post and click URL.

Returns the ads and insights: insights flag REJECTED ads (policy review) and ads still PENDING_APPROVAL.

Reddit Ads API: https://ads-api.reddit.com/docs/v3/

Input Schema

NameRequiredDescriptionDefault
ad_group_idNoReddit ad group id (from get_reddit_ad_groups) to limit the list to; empty means no ad group filter.
campaign_idNoReddit campaign id (from get_reddit_campaigns) to limit the list to; empty means no campaign filter.
include_copyNoWhen true, adds each ad's post: type (TEXT, IMAGE, VIDEO, CAROUSEL), headline, body, destination and media, one request per distinct post (at most 50 posts per call), so creative can be reviewed without opening Reddit.
ad_account_idNoReddit ad account id (from list_reddit_accounts). Empty uses reddit.ad_account_id from the config.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / ad_account_id / description
      Added value: +"Reddit ad account id (from list_reddit_accounts).\nEmpty uses reddit.ad_account_id from the config."
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Reddit ad group id (from get_reddit_ad_groups) to limit\nthe list to; empty means no ad group filter."
    • addedInput schema / properties / campaign_id / description
      Added value: +"Reddit campaign id (from get_reddit_campaigns) to limit\nthe list to; empty means no campaign filter."
    • addedInput schema / properties / include_copy / description
      Added value: +"When true, adds each ad's post: type (TEXT, IMAGE,\nVIDEO, CAROUSEL), headline, body, destination and media, one\nrequest per distinct post (at most 50 posts per call), so creative\ncan be reviewed without opening Reddit."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish the safe read-only profile (readOnlyHint=true, destructiveHint=false), so the description is not carrying the safety burden. It does add useful semantics about the insights flag surfacing REJECTED and PENDING_APPROVAL ads, but stops short of explaining pagination, request cost, or filtering behavior beyond that.

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

Conciseness4/5

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

Front-loaded with verb and resource, then the return semantics, in three short lines. The trailing Reddit Ads API URL is minor filler but low cost.

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, so return values need not be explained, and annotations cover safety. The description completes the picture by clarifying what the list and insights convey. Only the lack of routing guidance against sibling tools keeps it from a 5.

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 each of the four parameters documented inline (including the per-post request cost of include_copy). 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 ('List') and resource ('Reddit ads') plus the salient return fields (status, rejection_reason, post and click URL). It is clearly a read/list tool, but it does not explicitly differentiate itself from sibling readers such as get_reddit_performance or run_reddit_report.

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 explicit when-to-use or when-not guidance, and no alternative sibling is named. The presence of a campaign_id/ad_group_id filter hints at scoped listing, but the agent must infer when this tool beats get_reddit_performance or run_reddit_report.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.