Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reddit_comments

Retrieve flat public comments from a Reddit post by providing the post ID. Supports sorting and limiting the number of comments returned.

Instructions

Get Reddit post comments. Returns flat public comment entries from a Reddit post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesReddit post id or t3_ id
sortNoAccepted for compatibility: confidence, top, new, controversial, old, or qa. Public comment data is flat and may ignore sort.
limitNoMaximum comments returned, defaults to 25 and clamps to 100
depthNoAccepted for compatibility. Public comment data is flat and may ignore depth.
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that comments are flat and that sort/depth parameters may be ignored. However, it does not mention any side effects, rate limits, or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences with no waste. The first sentence states the purpose, the second adds important context about flat data. Each sentence earns its place.

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 tool with 4 parameters, all described in the schema, the description explains the output is flat comments. While no output schema exists, this provides sufficient context for a read tool. Could mention field structure but not necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying that sort and depth parameters are 'Accepted for compatibility' and may be ignored, which goes beyond the schema's property descriptions.

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 the verb 'Get' and the resource 'Reddit post comments', and notes it returns 'flat public comment entries'. This distinguishes it from siblings like reddit_post, reddit_search, and reddit_subreddit_posts.

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?

No guidance on when to use this tool vs alternatives. It does not mention when not to use it or provide any context for selection among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server