Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddits_posts

Fetch public posts from up to 10 combined subreddits with sorting, time-window, limit, and pagination controls for Reddit feed monitoring or research.

Instructions

List Reddit multi-subreddit posts. Returns public posts from a combined multi-subreddit feed. 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
sortNoSort: hot, new, top, or rising
timeNoTime window for top sort: hour, day, week, month, year, or all
afterNoReddit pagination token
limitNoMaximum posts, defaults to 25 and clamps to 100
subredditsYesComma-separated subreddit names, without r/, maximum 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "hot",
+  "new",
+  "top",
+  "rising"
+]
    • 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. Addedv1.1.0

TDQS

A3.6/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 add real operational context: public-only returns, a 503 + Retry-After throttling/retry protocol, and a source.type=redlib caveat about preserved fields and credit weights. It still omits auth requirements and general rate-limit behavior, but the error-handling disclosure is well above average.

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?

Four short sentences with the core purpose front-loaded and no filler. The 503/Retry-After sentence earns its place as actionable guidance, though the trailing redlib sentence is cryptic without external context.

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?

No output schema exists, so the description should describe return shape, but 'Returns public posts' is vague and pagination behavior is left entirely to the schema's 'after'/'limit' fields. Combined with the opaque redlib reference, an agent is not fully equipped, though the essentials for calling it are present.

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% (sort, time, after, limit, subreddits are all documented in the schema), so the baseline is 3. The description adds no syntax, format, or constraint details beyond what the schema already states.

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 ('List') and resource ('Reddit multi-subreddit posts') and clarifies scope with 'combined multi-subreddit feed'. The 'multi-subreddit' qualifier implicitly distinguishes it from the single-subreddit sibling reddit_subreddit_posts, but it never names that sibling explicitly.

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?

Usage is only implied: the 'multi-subreddit' framing suggests when it applies versus a single-subreddit tool, but there is no explicit when-to-use/when-not-to-use guidance and no alternative is named. An agent must infer the routing from the tool name.

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