Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_subreddit_search

Search a specific subreddit for posts, comments, or media matching a query. Sort by relevance, hot, top, or new and page through results with a cursor.

Instructions

reddit: Subreddit Search. GET /v1/reddit/subreddit/search. Search within a subreddit for posts, comments, or media matching a query Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "subreddit": "<subreddit>"
    },
    "name": "reddit_subreddit_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order. For posts/media: relevance, hot, top, new, comments. For comments: relevance, top, new
queryNoSearch query to find matching content
cursorNoCursor to get more results. Get 'cursor' from previous response.
subredditYesSubreddit name (e.g. 'Fitness', not 'r/Fitness' or a full URL)
timeframeNoTimeframe to filter results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose a detailed credit model: 1 credit on success, zero for errors, blocked, timed-out, invalid and cached requests. That is genuinely useful non-schema context. It omits other behavioral traits an agent would want, such as rate limits, authentication expectations, and how results differ in shape across posts/comments/media.

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

Conciseness3/5

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

The first two sentences are well front-loaded and waste nothing. The remaining credit-cost paragraph is long, boilerplate-heavy, and its final sentence ('charged only where that operation's published cost says so') is vague enough to add little, diluting an otherwise tight definition.

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

Completeness3/5

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

With five parameters, 100% schema coverage and no output schema, the input side is well covered by the schema. The description does not compensate for the missing output schema by indicating what a result looks like, and the note that results may be posts, comments or media hints at heterogeneous returns without explaining them.

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 and the schema already explains sort, query, cursor, subreddit and timeframe. The description adds a small amount beyond the schema by enumerating the content types searched (posts, comments, media), which clarifies what the sort and query parameters operate over. That is a modest but real increment over the structured fields.

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 and resource: 'Search within a subreddit for posts, comments, or media matching a query', plus the underlying route. The scoping phrase 'within a subreddit' implicitly separates it from the broader reddit_search, but it never names that sibling, so the differentiation is inferential rather than explicit.

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 description implies the usage context (subreddit-scoped rather than site-wide search) and the three content types it can target. However it gives no explicit when-to-use versus reddit_search or reddit_subreddit_details, and no prerequisites such as whether the subreddit must exist or be public.

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