Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_domain_posts

List public Reddit posts submitted from a linked domain, with sort, time, and pagination options to find and track shared content.

Instructions

List Reddit domain posts. Returns 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. If source.type is redlib, public fields and credit weights are preserved.

Input 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?

With no annotations, the description carries the burden and does meaningful work: it declares the read-only nature ("Returns public posts"), documents the 503 + Retry-After throttling contract with a retry instruction, and notes a source.type-dependent data-fidelity caveat. It still omits auth requirements and general error behavior, keeping it below a 5.

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?

Four tight sentences with the purpose front-loaded and no filler; the operational caveats are ordered sensibly after the core definition. The opening sentence is mildly redundant with the second but costs almost nothing.

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 read-only listing tool with no output schema, the description covers purpose, throttling behavior, and data provenance, which is enough for correct invocation. It could say more about pagination semantics and returned fields, but nothing essential to calling it is missing.

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% and all five parameters (sort, time, after, limit, domain) are documented in the schema itself, including enum values and the limit clamp. The description adds no parameter-level detail beyond the domain concept, 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 then sharpens the scope with "public posts submitted from a linked domain," which cleanly separates it from the subreddit- and user-scoped siblings. It never names a sibling alternative outright, so it falls short of 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?

The domain-scoping sentence implies when the tool applies (you want posts tied to a domain rather than a subreddit or user), but there is no explicit when-to-use, no prerequisites, and no named alternative such as reddit_search. Usage is left 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