Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

producthunt_leaderboard

Retrieve daily, weekly, monthly, or yearly Product Hunt leaderboard rankings by date or year/month/day/week. Returns the first page for trend and launch analysis.

Instructions

Retrieve Product Hunt leaderboard. Returns the Product Hunt leaderboard for a scope of daily (default), weekly, monthly or yearly, positioned with date (YYYY-MM-DD) or year, month, day and week. Only the first page is served, so a non-empty cursor returns an error. featured and order are accepted but do not change the default view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoDaily day override
dateNoAnchor date in YYYY-MM-DD format. Used to derive missing year/month/day/week values.
weekNoWeekly ISO week override
yearNoLeaderboard year override
monthNoDaily/monthly month override
orderNoRanking order override. Defaults to scope rank enum.
scopeNoLeaderboard scope: daily, weekly, monthly, yearly
cursorNoPagination cursor
featuredNoFeatured products only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "daily",
+  "weekly",
+  "monthly",
+  "yearly"
+]
  2. First observedv1.0.0

TDQS

A3.9/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 does disclose genuinely useful behavior: only the first page is served, a non-empty cursor produces an error, and featured/order are accepted but do not change the default view. It stops short of covering auth requirements or the shape of the returned data.

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 tight sentences, front-loaded with the core action, then scope/positioning, then the pagination caveat. Every sentence adds information and nothing is redundant.

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 9-parameter, zero-required read tool with no annotations and no output schema, the description covers scope, date positioning, pagination limits, and no-op parameters well. Minor gaps remain around the return shape and how the various date fields interact with scope, but nothing blocking.

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 already 100%, setting a baseline of 3, but the description adds real meaning beyond it: scope defaults to daily, date is the anchor that derives missing values, cursor triggers an error, and featured/order are no-ops. This is more than restating the schema.

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 ('Retrieve Product Hunt leaderboard') and enumerates the scope values, so the agent knows exactly what it returns. It does not explicitly name or contrast with siblings like producthunt_launches or producthunt_search, so differentiation is left to inference.

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?

Usage is implied through the scope/date mechanics (which scope and how to position it), giving the agent enough to call it correctly. However, there is no explicit when-to-use statement or named alternative for other Product Hunt endpoints, so routing guidance is incomplete.

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