Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_user_posts

Fetch and list public Reddit posts from a user's submitted feed, with pagination, limit controls, and fallback handling for throttling or source failures.

Instructions

List Reddit user posts. Returns normalized 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. Native-source failures can use the internal Redlib fallback; source.type is redlib and public fields/credit weights are preserved.

Input Schema

TableJSON 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

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 does useful work: it discloses the 503/Retry-After throttling contract, the Redlib fallback for native-source failures, and that source.type and credit weights are preserved. It omits any mention of pagination traversal or auth posture, but the error/fallback behavior is genuinely valuable context.

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?

Three sentences, front-loaded with the core purpose, then operational caveats. No filler, and the throttling/fallback notes are dense but relevant. Slightly terse on the fallback wording ("credit weights") but structurally sound.

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 exists, and the description compensates by describing return normalization ("normalized public posts") and the source/fallback semantics. Combined with complete parameter schema coverage for a simple 3-param read tool, an agent has enough to call it correctly.

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% – username (no u/), after (pagination token), and limit (default 25, clamps to 100) are all documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 posts") and narrows the scope to a single public user's submitted feed. It is unambiguous about what is returned, but it never names or contrasts with siblings like reddit_user_comments or reddit_subreddit_posts, which would push it to a 5.

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 only implied: passing a username to fetch that user's posts is obvious, but there is no explicit when-to-use/when-not guidance or pointer to reddit_user_comments as the alternative for comments. For a per-user feed tool this is adequate but leaves the alternative-selection decision to inference.

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