Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddit_comments

Fetch public comments from a subreddit's latest-comments feed with limit and pagination. Use it to collect flat Reddit comment entries for analysis.

Instructions

List Reddit subreddit comments. Returns flat public comment entries from a subreddit latest-comments 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
afterNoReddit pagination token
limitNoMaximum comments, defaults to 25 and clamps to 100
subredditYesSubreddit name, without r/

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / with_scores
      Removed value: -{
-  "description": "When true, source comment scores from old.reddit HTML rather than the default (slower)",
-  "type": "boolean"
-}
  2. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / with_scores
      Added value: +{
+  "description": "When true, source comment scores from old.reddit HTML rather than the default (slower)",
+  "type": "boolean"
+}
  3. 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 useful work: it discloses the return shape (flat public entries), the throttling contract (503 + Retry-After, wait and retry), and transparent fallback behavior (internal Redlib source with fields and credit weights preserved). It omits auth/permission requirements and any broader rate-limit or pagination semantics.

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?

Purpose is front-loaded in the first sentence, and the remaining sentences each add distinct operational value (return shape, throttle handling, fallback). Slightly jargon-heavy ('credit weights') but no filler.

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 3-param, no-annotation, no-output-schema list tool, the description covers what it returns, how to react to throttling, and resilience via fallback. Authentication expectations and cross-tool disambiguation are the remaining gaps, but nothing essential to calling it correctly is missing.

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 'after', 'limit' (default 25, clamps to 100), and 'subreddit' (without r/) are already fully documented. The description adds no extra meaning such as token lifetime or how pagination terminates, so the baseline 3 applies.

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 clear verb and resource (list comments) and scopes it to a subreddit latest-comments feed, with a note on the returned shape ('flat public comment entries'). It never names any sibling (reddit_comments, reddit_subreddit_posts, reddit_subreddits_posts, reddit_user_comments), so the agent must infer the boundary from the phrase 'subreddit latest-comments feed'.

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 implied by the scoping ('from a subreddit latest-comments feed') but there is no explicit when-to-use, when-not-to-use, or named alternative among the many reddit_* siblings. The retry/fallback sentences are operational rather than 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