Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_reddit_trending_item

Retrieves a single stored Reddit trending-post ranking record by post_uid, using the subreddit:date:rank key returned from a prior trending search.

Instructions

Get one Reddit trending-post record. Retrieves one stored subreddit-post ranking row by post_uid, the subreddit:date:rank key returned by datasets_reddit_trending_search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_uid": "<post_uid>"
    },
    "name": "datasets_reddit_trending_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_uidYesExact post_uid from a search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It discloses that this is a read of a stored record keyed by an identifier, implying a safe lookup, but says nothing about error behavior for missing keys, permissions, or row scope. Adequate but thin for an unannotated tool.

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?

Two compact sentences, front-loaded with the action and then the key semantics. The slight redundancy between 'Get' and 'Retrieves' is harmless; nothing is wasted.

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?

For a simple single-key lookup with 100% schema coverage and no output schema, this covers the essential input provenance. However, without annotations or an output schema it doesn't describe what the record contains, leaving the agent guessing about the return shape.

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% and the schema already explains post_uid, but the description adds real meaning by specifying the composite subreddit:date:rank format and that it must come from a search result, which the schema only gestures at.

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?

Specific verb (Get/Retrieves) and resource (one Reddit trending-post record / subreddit-post ranking row), and it distinguishes from the sibling search tool by name and by key provenance.

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?

Explicitly ties usage to post_uid values returned by datasets_reddit_trending_search, which tells the agent the prerequisite call. It doesn't state when not to use it or name alternatives beyond the search 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