Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_trends

Fetch trending Reddit posts across hot, new, rising, or top feeds. Specify sort order and time window to filter results, with pagination for larger datasets.

Instructions

List Reddit trends. Returns normalized public posts from broad Reddit hot, new, rising, or top feeds. For subreddit-specific trends, use /reddit/subreddit/{subreddit}/posts with sort=hot, sort=new, sort=rising, or sort=top. 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, rising, or top
timeNoTime window for top sort: hour, day, week, month, year, or all
afterNoReddit pagination token
limitNoMaximum posts, defaults to 25 and clamps to 100

Schema Changelog

Changes observed during successful MCP inspections.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return type ('normalized public posts') and the 503 retry behavior, which adds useful context. However, it does not disclose other behaviors like authentication requirements, rate limits beyond throttling, or whether the operation is read-only. The absence of annotations means more is expected, but the description does provide some valuable behavioral context.

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 with no filler: first states purpose, second gives alternative, third gives error handling. Each sentence earns its place. It could arguably be slightly more compact, but it is well-structured and front-loaded with the primary function.

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?

The tool is relatively simple (list of posts with pagination), and the description explains the resource and gives a sense of the return ('normalized public posts'). However, there is no output schema, so the description could mention fields or structure to help an agent know what to expect. For a list endpoint, this is acceptable but not exhaustive, so a 3 is fair.

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?

The schema provides complete documentation for all 4 parameters (100% coverage), including enums for sort and time, and descriptions for after and limit. The description adds little beyond the schema; it reiterates the sort values when describing the alternative, but that is redundant. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states a specific verb ('List'), a resource ('Reddit trends'), and the scope ('broad Reddit hot, new, rising, or top feeds'). It explicitly distinguishes from subreddit-specific trends by naming the alternative endpoint, so an agent can tell it apart from sibling reddit tools without opening schemas.

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

Usage Guidelines5/5

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

The description provides explicit when-not guidance by naming the exact alternative (`/reddit/subreddit/{subreddit}/posts`) and the conditions under which it should be used (subreddit-specific trends). It also gives error-handling behavior for 503 throttling, which is valuable operational 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