Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_search

Search Reddit posts by keyword, subreddit, sort, and time window, returning normalized public post entries with pagination.

Instructions

Search Reddit posts. Searches public Reddit content and returns normalized public post entries. A 503 with a Retry-After header means Reddit is temporarily throttling the request; wait that many seconds and retry. Native-source failures can use the internal Redlib fallback; source.type is redlib and public fields/credit weights are preserved.

Input Schema

TableJSON 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

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does so well: it discloses the 503 + Retry-After throttling contract, the Redlib fallback path for native-source failures, and that source.type becomes 'redlib' with public fields and credit weights preserved. Missing pieces like rate limits or pagination semantics beyond the token parameter keep it short of a 5.

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?

Three sentences, front-loaded with the core purpose, followed by return normalization and failure handling. Each sentence carries distinct information with no filler, though the fallback sentence is dense and could be slightly tighter.

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 6-parameter read tool with no output schema, the description covers purpose, scope, response shape at a high level, and failure/fallback behavior. The main gap is the absence of any guidance distinguishing its results from sibling reddit listing tools.

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%, with every parameter documented inline including enum values and clamping behavior, so the baseline is 3. The description adds no additional parameter meaning (nothing about sort/time interactions, subreddit scoping syntax, or pagination via 'after').

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 posts', and clarifies scope as 'public Reddit content' returning 'normalized public post entries'. It does not, however, distinguish itself from close siblings like reddit_subreddit_posts, reddit_domain_posts, or reddit_search's own restricted-search capabilities, so an agent gets a clear action but no sibling differentiation.

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?

The description never says when to use this tool versus the many sibling reddit_* tools (reddit_post, reddit_subreddit_posts, reddit_domain_posts, reddit_trends). The only conditional guidance is about retry behavior on failure, which is operational rather than tool-selection guidance.

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