Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reddit_user_posts

List public posts from a Reddit user's submitted feed. Accepts username, pagination token, and limit parameters.

Instructions

List Reddit user posts. Returns normalized public posts from a public Reddit user's submitted feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoReddit pagination token
limitNoMaximum posts, defaults to 25 and clamps to 100
usernameYesPublic Reddit username, without u/
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'normalized public posts' but doesn't explain normalization, pagination (despite the 'after' parameter), rate limits, or authentication needs. The description adds minimal behavioral context beyond the purpose.

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?

The description is concise with two sentences, no unnecessary words, and front-loaded with the primary purpose. Every sentence adds value without redundancy.

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

Completeness3/5

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

For a list tool with no output schema, the description provides basic purpose and return nature but lacks details on pagination behavior, response structure, or what 'normalized' entails. This is adequate for simple use but incomplete for complex scenarios.

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 baseline is 3. The description does not add any meaning beyond the schema; it repeats 'normalized public posts' but doesn't connect to parameters like 'after' or 'limit'. No additional parameter guidance.

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 tool lists Reddit user posts, specifying the resource ('Reddit user posts') and action ('List'), with scope ('public posts from a public Reddit user's submitted feed'). It distinguishes itself from sibling tools like reddit_user_comments (comments) and reddit_subreddit_posts (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 Guidelines3/5

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

The description implies usage for listing a user's posts but provides no explicit guidance on when to use this tool versus alternatives like reddit_search or reddit_subreddit_posts. No when-not-to-use or alternative mentions are included.

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