Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reddit_subreddit_posts

Retrieve posts from any Reddit subreddit. Specify sort order, time window, and limit to get normalized public data.

Instructions

List Reddit subreddit posts. Returns normalized public posts from a subreddit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort: hot, new, top, or rising
timeNoTime window for top sort: hour, day, week, month, year, or all
afterNoReddit pagination token
limitNoMaximum posts, defaults to 25 and clamps to 100
subredditYesSubreddit name, without r/
Behavior2/5

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

Without annotations, the description carries the full burden but only says it lists and returns normalized public posts. It does not disclose behavior like rate limits, authentication, pagination, error handling, or sorting specifics 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 a single concise sentence, which is efficient but lacks structure. It could be improved with bullet points or separate sections for clarity, but it is not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters and no output schema. The description only says 'returns normalized public posts' without specifying output structure, fields, or pagination details. It should provide more context about the return format and any constraints.

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?

The input schema already describes all 5 parameters with 100% coverage, so the description adds no additional meaning beyond 'List Reddit subreddit posts'. The baseline of 3 is appropriate as schema does the heavy lifting.

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 'List' and resource 'Reddit subreddit posts', specifying 'public posts' and 'normalized'. This distinguishes it from sibling tools like reddit_subreddit_comments and reddit_subreddit_about, which deal with comments and subreddit info, respectively.

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 is provided on when to use this tool versus alternatives such as reddit_subreddits_posts or reddit_search. There is no mention of prerequisites, scenarios, or exclusions.

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