Product Hunt MCP Server

search_posts

Search Product Hunt posts by query, with pagination and option to save cleaned results.

Instructions

Search Product Hunt posts. Returns cleaned data in TOON format.

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>"
    },
    "name": "search_posts"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search query
`first`	No	Number of posts (default: 10)
`after`	No	Cursor for pagination
`save_dir`	No	Directory to save cleaned JSON data
`max_items`	No	Max items to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'Returns cleaned data in TOON format' but does not explain what 'cleaned' means, the TOON format, pagination, rate limits, or any side effects. This is insufficient for a tool with 5 parameters.

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 two short sentences with no fluff. Each sentence serves a purpose: stating the action and noting the output format. It is concise, though could include more detail without harming conciseness.

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?

Given 5 parameters, no output schema, and many sibling tools, the description is too sparse. It does not explain pagination (after), the save directory functionality, or differentiate from similar tools beyond the verb 'search'. Lacks crucial context for effective tool selection.

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 coverage is 100%, so the baseline is 3. The description adds no meaning beyond the schema's parameter descriptions; it does not clarify the role of 'save_dir', 'max_items', or 'after' cursor beyond the schema.

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 states 'Search Product Hunt posts', which is a specific verb and resource. This clearly distinguishes it from sibling tools that are all 'get_*' for retrieving specific items.

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 does not explicitly state when to use search_posts versus alternatives. However, being the only search tool among siblings implies its usage for searching, earning a score of 3 for implied guidance.

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

Deploy Server