Skip to main content
Glama

Search Product Hunt launches by day, topic or text

producthunt
Read-only

Product Hunt launches: today's top launches, the newest in one topic (for example artificial-intelligence), or a text search over the newest launches. Each has name, tagline, votes, comments, launch time, links and topics. Today is the top 20 by ranking kept when posted on today's UTC date; search covers the newest 60 launches only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "producthunt"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to match in the name or tagline, for mode search
modeNotoday (default), topic or search
limitNoLaunches to return, 1 to 20, default 10
topicNoTopic slug for mode topic, e.g. artificial-intelligence

Output Schema

NameRequiredDescriptionDefault
dateNo
modeNo
noteNo
countNo
postsNo
sourceNo
scannedNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the hard limits that actually shape a call: 'today' is a ranked top 20 filtered to the current UTC date, and search only covers the newest 60 launches. It also states the paid-call model ($0.002 per successful call via x402 on USDC networks) and that failures are free — critical context an agent would not otherwise have.

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?

Front-loaded with the resource and the modes, then scoping constraints, then pricing — a sensible information order with no filler. The pricing sentence is long but is genuinely decision-relevant for an agent that must consider cost.

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

Completeness5/5

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

Given an output schema exists, the description needn't document return fields, yet it still summarizes them (name, tagline, votes, comments, launch time, links, topics). Combined with the mode limits and payment model, an agent has everything needed to call this correctly.

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%, so the baseline is 3, but the description earns more by explaining the semantics behind the parameters: what 'today' means in terms of ranking and UTC date, the 60-launch ceiling that applies to text search, and a concrete topic slug example. It does not restate the `limit` range or default, which the schema already covers.

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?

The description names a concrete resource (Product Hunt launches) and enumerates its three distinct modes — today's top launches, newest in a topic, and text search over newest launches — which map directly onto the `mode` parameter. An agent can tell exactly what the tool returns without opening the schema.

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?

The three modes are described with enough context to select between them (topic example 'artificial-intelligence' is given, search is scoped to newest launches). It stops short of explicit exclusions or comparisons to other search sources such as hn_search or arxiv, so routing between sources is left to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources