Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_reddit_trending_search

Search daily Reddit trending snapshots to find hot-feed post rankings by subreddit, date, or keyword and track trending history over time.

Instructions

Search the reddit-trending dataset. Searches daily snapshots of each tracked subreddit's hot-feed post order, stored in a search index (one document per subreddit × snapshot × rank) so history accumulates. With no date the latest snapshot is returned (today's trending); pair subreddit with sort=date_desc for a subreddit's trending history over time. There is no score or comment-count field — the underlying credential-free scraper does not expose vote counts, so rank reflects Reddit's own hot-feed order rather than a locally computed score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over the post title, max 256 characters
dateNoSnapshot date filter yyyy-MM-dd; defaults to the latest snapshot
pageNoPage number, defaults to 1
sortNoSort enum: rank, date_desc
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
subredditNoExact subreddit-name filter, max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "rank",
+  "date_desc"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description bears full disclosure burden and delivers: history accumulates across snapshots, there is no score or comment-count field, the scraper is credential-free, and rank reflects Reddit's own hot-feed order rather than a locally computed score. These caveats materially prevent an agent from misinterpreting results.

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, each earning its place: the lead states the resource, the second gives the two key usage patterns, and the third explains the rank caveat. No filler or redundancy.

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 6-parameter search tool with no annotations or output schema, the description is nearly complete: it covers the data model, default snapshot behavior, history retrieval, and rank semantics. It stops just short of describing the response shape or page/result boundaries, which are left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description adds value by explaining the date default behavior, the subreddit+sort=date_desc idiom, the meaning of rank, and the absence of vote fields. It does not restate the schema and gives agents parameter-combination guidance.

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?

Opens with a specific verb plus resource ('Search the reddit-trending dataset') and then defines exactly what is searched: daily snapshots of each tracked subreddit's hot-feed post order. The one-document-per-subreddit-snapshot-rank model separates it from sibling Reddit tools like reddit_search or reddit_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides concrete usage scenarios: omitting date returns the latest snapshot, and pairing subreddit with sort=date_desc yields a subreddit's trending history. It does not name alternatives or explicitly say when not to use this tool, but the context is clear.

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