Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Find subreddits

search_subreddits
Read-onlyIdempotent

Find subreddits by topic or partial name, including name-prefix matches when the exact community is unknown. Use it to discover communities, not posts, then browse or search within them.

Instructions

Find communities about a topic, and names that start with the query.

Combines Reddit's description search with a name-prefix lookup, so a guess such as "dremio" (no such subreddit) still surfaces r/dremio_lakehouse. Shows subscribers, creation date, NSFW and access flags, and the public description. Use it when unsure of a community's exact name, then pass the name to browse_subreddit, search_reddit(subreddit=...) or get_subreddit_info. It finds communities, not posts.

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": "search_subreddits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum communities per section, 1 to 50.
queryYesTopic words or a partial community name, up to 512 characters.
include_nsfwNoShow posts, comments and communities Reddit marks NSFW (18+). Off by default; hidden items are counted in the output. A server setting can keep them hidden even when true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, open-world, non-destructive operation. The description adds meaningful behavior beyond that: it explains the combined description/name-prefix search, notes that a guessed name can surface a similarly named community, and lists the result fields such as subscribers, creation date, NSFW and access flags, and public description. It does not discuss rate limits or pagination, keeping it below a perfect score.

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 front-loaded with the core action and scope, then adds the distinctive search mechanics, result fields, and handoff guidance. Every sentence contributes useful information, and there is no redundant restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter search tool with no output schema, the description covers purpose, search behavior, result contents, scope boundaries, and next-step alternatives. The remaining details such as limit enforcement and NSFW server behavior are already covered by the schema, so nothing essential is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning for the main query parameter by describing name-prefix matching and giving the concrete 'dremio' to 'r/dremio_lakehouse' example. The limit and include_nsfw parameters are documented only in the schema, so the description does not fully supplement all parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Find communities') and immediately distinguishes this tool from post-search siblings by saying 'It finds communities, not posts.' It also explains the two search modes, topic description search and name-prefix lookup, so an agent can distinguish it from search_reddit and related tools.

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

Usage Guidelines5/5

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

It gives an explicit usage condition: 'Use it when unsure of a community's exact name.' It then names the follow-up alternatives, browse_subreddit, search_reddit(subreddit=...), and get_subreddit_info, so the agent knows both when to choose this tool and what to do after finding a community.

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