Skip to main content
Glama
Reddit Buddy MCP

Reddit Buddy MCP

by karanb192

find_subreddits

Read-only

Locate subreddits by topic and verify names before browsing or searching Reddit; returns confirmed candidates, search suggestions, subscriber counts, NSFW flags, and status details.

Instructions

Find subreddits for a topic and check subreddit names before you use them. Call this before browse_subreddit or search_reddit with any subreddit you are not sure exists. Give query as 2 to 4 keywords (not a sentence) and up to 10 candidate names. results: your confirmed candidates first, then Reddit's own search suggestions, each with a url, subscribers with an as-of time, an nsfw flag, its type (restricted means most accounts cannot post there) and its source. not_found: candidates Reddit did not return, or that are not valid names. unavailable: names that exist but are private, quarantined or banned; do not browse those. If the name check itself fails, candidates come back with confirmed_exists false, meaning unchecked. NSFW subreddits and suggestions under min_subscribers are left out and counted. Needs Reddit API credentials.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, range (1-50). Most Reddit search suggestions to return. Change ONLY IF user asks.
queryYes2 to 4 keywords for the topic, as you would type them in a search box (e.g., "budget cooking", "mechanical keyboards"). NOT a sentence: Reddit matches words, so long phrases return unrelated subreddits.
candidatesNoUp to 10 subreddit names you think fit, without r/. Each is checked against Reddit; names Reddit does not return come back in not_found.
include_nsfwNoNSFW subreddits left out are counted in nsfw_hidden. Leave unset to follow the server setting (NSFW hidden unless the server owner chose otherwise). Set true ONLY IF the user asks for NSFW content; set false to hide it. No effect on a server set to never return NSFW.
min_subscribersNoDefault 1000. Search suggestions with fewer subscribers are left out and counted in small_hidden; your candidates are never filtered by size. Lower it ONLY IF the user wants niche or new communities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial operational context: the results/not_found/unavailable triage, that unavailable means private/quarantined/banned and must not be browsed, that a failed check yields confirmed_exists=false (unchecked), and that NSFW/small suggestions are filtered and counted. It also states the Reddit API credential requirement. The only slight gap is no pagination or return-ordering beyond 'confirmed first'.

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 the action and the ordering rule, and the results/not_found/unavailable breakdown is efficient. The prose is telegraphic and dense in places, but nearly every sentence carries actionable information.

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?

With no output schema, the description must explain return shape, which it does field-by-field (url, subscribers with as-of time, nsfw flag, type, source, plus hidden counts). For a read-only lookup tool with five parameters, an agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds real meaning on top: candidates are names without r/ that get checked and never size-filtered, while min_subscribers only affects suggestions; include_nsfw has no effect on a never-NSFW server. That clarifies interactions between parameters that the schema documents only individually.

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?

States a specific verb and resource ('Find subreddits for a topic') plus a second action ('check subreddit names'), and explicitly positions itself relative to browse_subreddit and search_reddit. An agent can distinguish it from siblings without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit precondition: call this before browse_subreddit or search_reddit with any subreddit you are not sure exists. It also constrains parameter changes ('Change ONLY IF user asks', 'Lower it ONLY IF'), though it does not state when to skip subreddit lookup entirely (e.g., already-known names).

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