Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List ads

reddit_ads_list_ads
Read-only

Retrieve and filter ads from a Reddit Ads account using multiple criteria like campaign, ad group, or status. Supports pagination to fetch large result sets.

Instructions

List ads in an ad account. Filters are OR within a parameter and AND across parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reddit_ads_list_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFilter by ad IDs
max_pagesNoFollow pagination.next_url up to this many pages and merge results (default 1)
page_sizeNoItems per page (usually max 1000)
page_tokenNoPage token from a previous pagination.next_url
ad_group_idNoFilter by ad group IDs
campaign_idNoFilter by campaign IDs
ad_account_idNoAd account ID (t2_... or a2_...). Defaults to REDDIT_ADS_ACCOUNT_ID.
effective_statusNoFilter by effective status, e.g. ACTIVE, REJECTED, PENDING_APPROVAL
configured_statusNoFilter by configured status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds a useful behavioral detail about filter combination logic (OR within a parameter, AND across parameters), but it does not disclose return format, pagination behavior, or rate limits.

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 two sentences, front-loads the primary action, and every word earns its place. It efficiently conveys the core purpose and the filter combination rule without redundancy.

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?

Given the 9-parameter schema with full documentation and annotations covering safety, the description is largely sufficient for an agent to call the tool. It omits any description of return values or pagination summary, but the schema itself documents pagination parameters thoroughly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining how multi-value array filters combine: OR within a parameter and AND across parameters. This is meaningful semantics not present in the individual parameter descriptions.

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 ads') and scopes it to 'in an ad account,' which clearly distinguishes it from create_ad, update_ad, and get_ad. However, it does not explicitly name sibling alternatives or clarify when this is preferred over related listing tools like list_ad_groups.

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 gives no explicit when-to-use or when-not-to-use guidance, and it does not mention alternatives such as get_ad for a single ad or list_ad_groups for ad group listings. The purpose is implied by the verb 'List ads,' but there is no routing context.

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

Deploy Server

Other Tools