Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_user_comments

Fetch a public Reddit user's comments feed as flat JSON entries, with pagination and retry guidance when Reddit throttles requests.

Instructions

List Reddit user comments. Returns flat public comment entries from a public Reddit user's 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
usernameYesPublic Reddit username, without u/

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 behavioral burden and adds useful operational context: 503 Retry-After throttling semantics, a Redlib fallback for native-source failures, and preservation of public fields and credit weights. It doesn't state auth requirements explicitly, though 'public' implies none, and pagination behavior is left to 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.

Conciseness4/5

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

Four sentences that are front-loaded with the core purpose, followed by return format and two operational notes. No filler, though the final fallback sentence is somewhat technical and could be trimmed.

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 simple list tool with a fully documented schema and no output schema, the description covers purpose, return shape, throttling, and fallback behavior. Only minor gaps remain, such as explicit pagination usage guidance for the 'after' parameter.

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 three parameters including username format, after token, and limit defaults/clamps. The description adds no parameter-level detail beyond what the schema provides.

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 (List) and resource (Reddit user comments) and clarifies these are flat public entries from a user's comments feed. It distinguishes from a generic comments tool but does not explicitly differentiate from close siblings like reddit_user_posts or reddit_comments.

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?

Provides operational retry advice but no guidance on when to use this tool versus alternatives such as reddit_user_posts or reddit_comments. The condition that selects this tool (wanting a user's comments rather than posts) is only implied by the name and first sentence.

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