Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_user_posts

Fetch public Reddit posts from a user's submitted feed by username, with pagination and limit controls.

Instructions

List Reddit user posts. Returns public posts from a public Reddit user's submitted 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 posts, 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 score and comment_count 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 score and comment_count from old.reddit HTML rather than the default (slower)",
+  "type": "boolean"
+}
  3. Addedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add real behavior: a 503 with Retry-After means throttling and should be retried after that many seconds, and source.type=redlib preserves public fields and credit weights. It stops short of stating read-only semantics explicitly or pagination behavior beyond the schema's 'after' token.

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?

Three sentences, all front-loaded and earning their place: purpose first, then the retry/rate-limit operational note, then the redlib caveat. No filler.

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?

No output schema, so the description must convey the return profile, and it does identify the result as public posts from a submitted feed plus the rate-limit failure mode. Slightly thin on what individual post fields look like, but adequate for a read-only list tool.

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 username, after, and limit are already fully documented in the schema. The description adds little parameter-level meaning beyond reiterating that posts come from a public user's submitted feed.

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?

States a specific verb (List) and resource (Reddit user posts) and scopes it to a public user's submitted feed. The agent can distinguish this from reddit_user_comments and reddit_subreddit_posts without opening the schema.

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?

Usage is implied by 'public posts from a public Reddit user's submitted feed', but there is no explicit when-to-use guidance nor any naming of the sibling tool (reddit_user_comments) that would be the alternative for a user's comment history.

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