Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

producthunt_leaderboard

Fetch Product Hunt leaderboard rankings for daily, weekly, monthly, or yearly periods. Use date, scope, and pagination parameters to get structured ranking data.

Instructions

Retrieve Product Hunt leaderboard. Fetches Product Hunt leaderboard data for daily, weekly, monthly, or yearly scopes via Product Hunt GraphQL.

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

C2.9/5.0
Behavior2/5

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

With no annotations present, the description carries the full burden of behavioral disclosure, and it provides only 'fetches data via Product Hunt GraphQL.' It does not disclose default behavior when no parameters are supplied, pagination behavior, output shape, or any rate-limit or authentication considerations.

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?

The description is short and front-loaded, with the core verb and resource in the first sentence. The second sentence is slightly redundant but adds the scope list and GraphQL context, so the overall size is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 9 optional parameters, no output schema, and no annotations, so the description should clarify defaults, required combinations, and return expectations. It only says 'fetches leaderboard data,' leaving an agent unsure whether a zero-argument call is valid, what the default scope is, or what the response will contain.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description itself adds no parameter-level meaning, matching the baseline of 3 rather than exceeding it.

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 clearly states the verb ('Retrieve'/'Fetches') and resource ('Product Hunt leaderboard'), and names the supported scopes: daily, weekly, monthly, and yearly. It is unambiguous about what the tool does, though it does not differentiate it from sibling Product Hunt tools such as producthunt_launches or producthunt_search.

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 gives no explicit guidance on when to use this tool versus alternatives, and it names no excluded cases. The scope list implies utility for time-based leaderboards, but an agent gets no help deciding between this and sibling Product Hunt tools.

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