Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_search

Search Reddit posts and comments by query, optionally limiting results to a subreddit and filtering by sort order or timeframe.

Instructions

reddit: Search. GET /v1/reddit/search. Search Reddit for posts or comments. Anonymous search looks in one subreddit: pass subreddit, or a single-word query, which is also used as the subreddit. sort and timeframe apply where the archive supports them. An empty page costs 0 credits. Search does not return upvote ratios. Use /v1/reddit/post for a post's upvote_ratio. Costs 1 credit when it succeeds. Costs 0 credits when posts is empty. 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": {
      "query": "<query>"
    },
    "name": "reddit_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Comment search supports relevance, new, and top; comment_count is for post search only.
trimNoSet true for a trimmed response.
afterNoUsed to paginate to next page
queryYesSearch query
filterNoSearch posts or comments
subredditNoLimit the search to this subreddit.
timeframeNoPost search timeframe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does unusually well: it discloses credit costs on success, on empty pages, on errors, blocked/timed-out requests, invalid requests and cache hits, plus the anonymous-search scoping rule and the missing upvote_ratio field. The only weakness is internal tension between "Costs 0 credits when posts is empty" and the closing sentence saying a not-found or empty result is charged where the published cost says so, which muddies rather than contradicts the billing rule.

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 functional content is front-loaded and tight, but the billing paragraph repeats the empty-result rule three times ("An empty page costs 0 credits", "Costs 0 credits when posts is empty", and the closing not-found/empty sentence) and the final sentence is boilerplate that reads as hedging.

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 7-parameter tool with no annotations and no output schema, the description covers cost, scoping, sort/timeframe limits and the missing upvote_ratio well. Remaining gaps are modest: no mention of pagination via `after`, no guidance on valid `filter` values, and no hint at response shape beyond "posts" being possibly empty.

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; the description earns an extra point by explaining that subreddit can be supplied directly or derived from a single-word query, and by caveating that sort and timeframe only apply where the archive supports them. It adds nothing about how `filter` encodes posts vs comments or what `trim` changes, which the schema also leaves vague.

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 Reddit for posts or comments" over GET /v1/reddit/search. It implicitly separates itself from reddit_post by noting that upvote ratios require that endpoint, but it never distinguishes itself from the sibling reddit_subreddit_search, leaving one obvious overlap unresolved.

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?

Gives real conditional guidance for the anonymous case (pass subreddit, or a single-word query that doubles as the subreddit) and redirects to /v1/reddit/post for upvote_ratio. It does not say when to choose this over reddit_subreddit_search or how post search differs from comment search, so the alternative-selection guidance is partial.

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