Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddits_posts

List combined public posts from up to 10 Reddit subreddits, with sort, time, and limit filters, to collect community content for monitoring or analysis.

Instructions

List Reddit multi-subreddit posts. Returns normalized 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. 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
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.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 well: it documents 503 + Retry-After throttling behavior, the Redlib fallback on native-source failure, and the preserved source.type/credit weights. It omits auth requirements and return shape, but the behavioral disclosure is unusually rich for a read tool.

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 sentences, front-loaded with purpose and return description before the operational notes. Every sentence earns its place; the only mild bloat is the credit-weights clause, which is tangential to invocation.

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 5-param read-only listing tool with no output schema, the description covers purpose, return nature ('normalized public posts'), and failure/fallback handling. Return-field detail is left implicit, but the behavioral coverage is sufficient for correct invocation.

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 the schema already documents all five parameters (sort, time, after, limit, subreddits). The description adds no syntax or format detail beyond the schema, which is the correct baseline when structured data does the heavy lifting.

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 ('List Reddit multi-subreddit posts') and immediately scopes it as a 'combined multi-subreddit feed', which distinguishes it from the singular reddit_subreddit_posts sibling. It is clear what the tool returns, though it does not explicitly name the sibling it replaces.

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 'multi-subreddit' framing implies when to prefer this over the single-subreddit variant, but there is no explicit when-to-use/when-not guidance and no named alternatives. The retry/fallback notes are operational rather than routing 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