Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reddit_domain_posts

List public Reddit posts from a linked domain, with sort, time, and pagination controls to return normalized JSON.

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.

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

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that posts are 'normalized' and gives a useful 503/Retry-After handling note, which adds value beyond the schema. However, it does not disclose rate limits, authentication requirements, pagination behavior, or the exact output structure, which are relevant for a list operation.

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 exactly two sentences: the first states the core purpose, the second provides actionable error-handling guidance. It is front-loaded, free of fluff, and every sentence earns its place.

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?

The description covers the tool's basic function and one error case, but it is thin on broader context. There is no output schema, yet the description only vaguely says 'normalized public posts' without hinting at fields or pagination. It also lacks any comparison to sibling Reddit tools, which would help an agent decide when to call this. Given the moderate complexity (5 params, no output schema), more context would be beneficial.

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?

The schema fully documents all five parameters with descriptions and enum values (100% coverage), so the baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides; it only restates that posts are from a linked domain.

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 clear verb ('List') and resource ('Reddit domain posts'), and clarifies it returns posts 'submitted from a linked domain'. This distinguishes it from subreddit-specific tools like reddit_subreddit_posts, but it does not explicitly name alternatives or contrast them, so it stops 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus other Reddit tools (e.g., reddit_subreddit_posts, reddit_search). It only states what it does, leaving the agent to infer appropriate contexts. There are no exclusions or alternative hints.

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