Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt launches

product_hunt_launches_list
Read-onlyIdempotent

Fetch Product Hunt launches for today or a selected day, week, month, or year, with scores and ranks to analyze startup trends by date.

Instructions

List Product Hunt launches for today or a chosen day, week, month or year, with scores and ranks. Optional inputs: today, year, month, week, day and 1 more. 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_launches_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoDay of the month, 1 to 31.
weekNoISO week, 1 to 53.
yearNoYear, 2010 to 2100.
monthNoMonth, 1 to 12.
todayNoToday's launches. Default when no date is given. Cannot be combined with a date.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results come back as a list and that a cursor is used when paginated, which is modest but genuine context. It says nothing about ordering, result caps, or whether the returned scores/ranks are point-in-time snapshots.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Opening sentence is front-loaded and earns its place. The second sentence duplicates what the fully documented schema already says and includes the sloppy 'and 1 more', which is wasted space in an otherwise short definition.

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?

With nine parameters but 100% schema coverage, rich annotations, and no output schema, the description covers enough: what is listed, the time scoping, the default, and the pagination mechanism. The remaining gap is sibling differentiation and result-shape detail, both minor here.

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 explains ranges, defaults, and even the cursor and context/conversation_id conventions. The description's parameter sentence restates parameter names and then degrades into '1 more', which adds no meaning and hints at incompleteness rather than elaborating.

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 gives a specific verb and resource ('List Product Hunt launches') plus the supported time granularities and the fact that scores and ranks come back. An agent can tell it apart from a get or search sibling, but nothing in the text distinguishes it from product_hunt_posts_list or product_hunt_leaderboard_list, which plausibly overlap.

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?

It states a useful default ('today' when no date is given) and an exclusion ('cannot be combined with a date'), which is real usage guidance for parameter selection. It offers no guidance on when to prefer this over the leaderboard, posts, or search siblings, so selection between alternatives is left to inference.

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