Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_search

Search public Reddit posts by keyword, optionally limiting results to a subreddit and filtering by sort or time window to find relevant discussions and community insights.

Instructions

Search Reddit posts. Searches public Reddit content and returns public post entries. A 503 with a Retry-After header means Reddit is temporarily throttling the request; wait that many seconds and retry. If source.type is redlib, public fields and credit weights are preserved.

Input Schema

NameRequiredDescriptionDefault
qYesSearch keywords
sortNoSort: relevance, hot, new, top, or comments
timeNoTime window for top/comments sorts: hour, day, week, month, year, or all
afterNoReddit pagination token
limitNoMaximum posts, defaults to 25 and clamps to 100
subredditNoRestrict search to a subreddit name, without r/

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "hot",
+  "new",
+  "top",
+  "comments"
+]
    • addedInput schema / properties / time / enum
      Added value: +[
+  "hour",
+  "day",
+  "week",
+  "month",
+  "year",
+  "all"
+]
  2. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / with_scores
      Removed value: -{
-  "description": "When true, source score and comment_count from old.reddit HTML rather than the default (slower)",
-  "type": "boolean"
-}
  3. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / with_scores
      Added value: +{
+  "description": "When true, source score and comment_count from old.reddit HTML rather than the default (slower)",
+  "type": "boolean"
+}
  4. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses rate-limit behavior (503 + Retry-After) and that only public content is returned, which is genuine added value. However, the closing note about source.type=redlib preserving 'public fields and credit weights' is cryptic and unexplained, and it omits other behavioral facts such as whether any auth is needed.

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?

Purpose and output scope are front-loaded, followed by a focused retry note. It is appropriately short, though the final sentence about redlib credit weights is unclear and does not clearly earn its place.

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?

There is no output schema and no annotations, so the description must carry more. It covers return scope and rate limiting but leaves pagination behavior, result shape, and tool-selection context unaddressed for a 6-parameter search tool.

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 q, sort, time, after, limit, and subreddit are all documented in the schema with enum values. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 (Reddit posts) plus the output scope (public post entries). It is clearly distinguishable from read-specific siblings like reddit_post or reddit_subreddit_posts, but it does not name any sibling to disambiguate itself explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this general search vs the many sibling listing tools (reddit_subreddit_posts, reddit_user_posts, reddit_trends, reddit_domain_posts). The only operational guidance is the 503 retry note, which is about error handling, not tool selection. Usage context is left entirely to inference.

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