Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_domain_posts

List public Reddit posts submitted from a specific domain, with sort, time, and pagination controls. Use it to monitor domain mentions and track submitted links.

Instructions

List Reddit domain posts. Returns normalized public posts submitted from a linked domain. 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
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
domainYesDomain hostname, without scheme or path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "hot",
+  "new",
+  "top",
+  "rising"
+]
    • addedInput schema / properties / time / enum
      Added value: +[
+  "hour",
+  "day",
+  "week",
+  "month",
+  "year",
+  "all"
+]
  2. 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"
-}
  3. 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"
+}
  4. Addedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers meaningfully: it discloses the 503 + Retry-After throttling contract, the Redlib fallback path, and that source.type becomes 'redlib' with public fields and credit weights preserved. It omits auth requirements, rate limits beyond the 503 case, and pagination semantics for 'after'.

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, purpose first and operational caveats after, with no filler. Could be trimmed slightly by merging the throttling and fallback notes, but every sentence carries substantive information.

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 list tool with 100% schema coverage, no output schema, and no annotations, the description covers purpose, source semantics, error handling, and fallback behavior well. The remaining gap is that it doesn't route the agent away from sibling Reddit tools, which would matter given the many reddit_* siblings.

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 the schema already documents sort, time, after, limit, and domain (including enum values and the 100 clamp). The description adds no parameter-level meaning beyond the schema, 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?

States a specific verb and resource ('List Reddit domain posts') and clarifies scope as 'posts submitted from a linked domain', which distinguishes it from subreddit- or user-based siblings. However, it never names the closest alternatives (reddit_subreddit_posts, reddit_search, reddit_user_posts) so the differentiation is inferred rather than stated.

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 the 'domain' scoping (use when you have a hostname, not a subreddit or user), but the description never says when to prefer this tool over reddit_subreddit_posts or reddit_search. It does provide useful operational guidance for throttling and fallback, but no when/when-not routing.

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