Search Product Hunt
product_hunt_search_listSearch Product Hunt products, users, posts, topics, and categories by query to find relevant listings and profiles; use cursor pagination to retrieve more results.
Instructions
Search Product Hunt products, users, posts, topics and categories, cursor-paged. Requires query. 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": {
"query": "<query>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "product_hunt_search_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | What to search: `all` (default), `product`, `user`, `post`, `topic` or `category`. | |
| query | Yes | Required. What to search for, e.g. `notion` or `ai agents`. | |
| cursor | No | Cursor from `page.nextCursor` of the previous response. It only works with the same endpoint and filters. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| llm_model | Yes | The 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_id | No | Echo 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. |