Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt leaderboard

product_hunt_leaderboard_list
Read-onlyIdempotent

List Product Hunt leaderboards by day, week, month, or year to track top products and paginate results with a cursor.

Instructions

List the Product Hunt leaderboard for today or a chosen day, week, month or year. Optional inputs: year, month, week, day and cursor. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "product_hunt_leaderboard_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoDay of the month, 1 to 31.
weekNoISO week, 1 to 53.
yearNoYear, 2010 to 2100.
monthNoMonth, 1 to 12.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same endpoint and filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely behavioral fact — results are a paginated list and `cursor` should be used to continue — but says nothing about ordering, what a leaderboard entry contains, or which timezone defines "today", which matters for a time-scoped ranking.

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?

Two sentences, front-loaded with the purpose, then inputs, then return behavior. No filler and no repetition of annotation-derived facts.

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?

There is no output schema, so the description is the only place the return shape could be characterized, yet it only says "a list". For a read-only, annotation-rich tool this is largely adequate, but the missing detail on what a leaderboard entry looks like and on filter interaction leaves a real gap.

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 all eight parameters are already documented in the schema, and the description merely echoes the four period inputs plus `cursor`. It adds only marginal meaning beyond the schema — the implicit default of "today" — and does not explain how filters combine (e.g. whether `week` and `day` are mutually exclusive or nested).

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?

"List the Product Hunt leaderboard" states a specific verb and resource, and the time-granularity clause (day/week/month/year) sharpens the scope. It does not name a sibling alternative, so the agent has to infer the distinction from the resource noun alone (e.g. vs. product_hunt_posts_list or polymarket_leaderboard_list).

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?

The description implies the usage condition (want a ranked leaderboard for a given period, defaulting to today) but states no explicit when-to-use vs. when-not, and gives no guidance on choosing between this and the sibling list/get tools. The implied default of "today" when no period is supplied is useful but left implicit rather than stated.

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