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

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search communities

reddit_ads_search_communities
Read-only

Search subreddits by name or topic to find communities for Reddit Ads targeting. Helps advertisers identify relevant audiences for campaigns.

Instructions

Search subreddits for targeting by name or topic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "reddit_ads_search_communities"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text
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

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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it searches subreddits for targeting, but does not disclose pagination behavior, result format, or auth requirements beyond what the annotations imply.

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 front-loaded sentence with zero waste. It leads with the verb and resource and immediately adds the targeting context.

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 search tool with fully described parameters and annotations covering read-only/open-world behavior, the description is nearly sufficient. It could mention that results are communities/subreddits, but the name and purpose make that clear enough for invocation.

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 all four parameters are already documented in the schema. The description only loosely maps 'name or topic' to the query parameter and adds no syntax or format details beyond what the schema provides.

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 (Search) and resource (subreddits/communities) plus the targeting purpose by name or topic. However, it does not explicitly distinguish itself from sibling tools like reddit_ads_get_communities or reddit_ads_suggest_communities.

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?

The phrase 'for targeting by name or topic' implies the intended use case for ad targeting. There is no explicit when-to-use versus alternatives or any exclusion guidance, so it remains implied rather than stated.

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