Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddits_posts

Fetch normalized public posts from multiple subreddits at once. Combine up to 10 subreddit feeds, sort by hot, new, top, or rising, and paginate with tokens.

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.

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

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the behavioral disclosure burden. It discloses that posts are 'normalized public posts', that the feed is a combined multi-subreddit feed, and it gives concrete 503/Retry-After handling guidance. This is useful behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly scoped sentences. The core purpose is front-loaded, and the rate-limit retry guidance is the only secondary detail included. Every sentence earns its place without redundant content.

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?

The combination of a fully documented schema, a clear statement of what the tool returns, and explicit rate-limit handling is sufficient for an agent to select and invoke the tool correctly. The lack of an output schema is partially mitigated by describing the posts as 'normalized public posts', though exact returned fields are still unspecified.

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 and their constraints. The description adds no additional parameter-level meaning beyond restating the multi-subreddit concept, which keeps this at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('List') and a specific resource ('Reddit multi-subreddit posts'), and clarifies that it returns a combined feed. This differentiates it from sibling tools like reddit_subreddit_posts, reddit_domain_posts, and reddit_search, even without naming them.

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 phrase 'combined multi-subreddit feed' implies when to use the tool, and the required `subreddits` parameter reinforces that. However, the description does not explicitly mention alternatives such as reddit_subreddit_posts for single-subreddit queries or otherwise state when not to use this tool.

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