Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_subreddit_comments

Retrieve public Reddit subreddit comments as flat entries, with pagination and limits, to collect discussion data or track community activity.

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. If source.type is redlib, public fields and credit weights are preserved.

Input 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.5/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 delivers real value: it discloses the return shape (flat public comment entries), a concrete throttling behavior (503 with Retry-After → wait and retry), and a redlib source caveat about preserved fields and credit weights. It omits pagination semantics for the `after` token and any auth/rate details beyond throttling.

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 tight sentences, front-loaded with the core purpose and then layering return shape, error handling, and a source caveat – each sentence carries information. Slightly dense 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 read-only list tool with no annotations and no output schema, the description covers return shape, throttling recovery, and a source quirk, leaving little an agent needs missing. Only pagination behavior and rate/auth context are absent.

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 `subreddit`, `limit` (default 25, clamps to 100), and the pagination token. The description adds no additional parameter syntax or format meaning, making the baseline 3 appropriate.

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+resource ("List Reddit subreddit comments") and clarifies scope via "from a subreddit latest-comments feed," which naturally separates it from sibling tools like reddit_user_comments and reddit_subreddit_posts. However, it never names an alternative sibling outright, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no comparison to alternatives such as reddit_comments, reddit_user_comments, or reddit_subreddits_posts, and no stated exclusions or prerequisites beyond the implied subreddit scoping. The agent is left to infer which Reddit comment tool fits.

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