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 by subreddit, date, or title to track hot-feed post rankings and view a subreddit's trending history over time.

Instructions

Search the reddit-trending dataset. Searches daily snapshots of each tracked subreddit's hot-feed post order (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, so rank reflects Reddit's own hot-feed order rather than a locally computed score. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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.3/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 mostly does: it discloses the absence of score/comment-count fields, that rank is Reddit's own hot-feed order (not a computed score), and a full billing model (1 credit per record, min 2, empty result costs 2). Auth/rate-limit behavior beyond billing is not covered, hence not 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?

Front-loaded with purpose, then data model, then usage, then billing. Five sentences each of which contributes distinct information; the 'so history accumulates' clause is slightly redundant but the overall size is justified by the complex billing and snapshot semantics.

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-param search tool with no annotations and no output schema, the definition covers the data model, key parameter behaviors, ranking semantics, and cost. The main residual gap is return-field structure, which is not described (though 'rank' is explained).

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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the 'date' default (latest snapshot), the subreddit+sort=date_desc pairing, and what 'rank' actually means. It adds real meaning over the schema text.

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?

States a specific verb (search) and resource (reddit-trending dataset) and pins down the data model precisely: one document per subreddit × snapshot × rank. That granularity lets an agent distinguish it from siblings like reddit_subreddit_posts or reddit_trends without opening either schema.

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?

Gives concrete when-to-use patterns: no 'date' returns today's trending, while pairing 'subreddit' with sort=date_desc yields a subreddit's trending history. It names no alternative sibling tools explicitly, so it stops short of the explicit when-not/alternatives bar, but the conditional guidance 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