Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

reddit_user_comments

Retrieve public Reddit user comments by username, with pagination and limit options, returning flat entries for analysis or monitoring.

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. 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
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.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 usefully discloses that entries are public and flat, that a 503 with Retry-After indicates throttling requiring a wait, and that redlib sources preserve public fields and credit weights. It could say more about authentication or pagination behavior, but the throttling and source caveats are valuable 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.

Conciseness4/5

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

The description is front-loaded with the purpose and return nature, followed by useful operational caveats. It is reasonably sized with little waste, though the redlib note is niche.

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 three-parameter public feed tool with no output schema and no annotations, the description covers purpose, return shape, throttling behavior, and a source-specific caveat. It is complete enough for selection and invocation, though it does not enumerate returned comment fields.

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 username, limit, and after. The description adds no parameter-specific syntax or semantics beyond what the schema provides, 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?

The description states a specific verb and resource: "List Reddit user comments" and "flat public comment entries from a public Reddit user's comments feed." It is clearly distinct from post-related siblings by focusing on a user's comment feed, though it does not explicitly contrast with reddit_user_posts.

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 intended use is implied by "public Reddit user's comments feed," but there is no explicit guidance on when to choose this over reddit_comments, reddit_user_posts, or other Reddit comment tools. No exclusions or alternatives are named.

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