Product Hunt MCP Server

get_posts

Retrieve Product Hunt posts filtered by featured status, topic, date range, or ranking order. Returns cleaned data for analysis.

Instructions

Get Product Hunt posts with filters. Returns cleaned data in TOON format.

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": "get_posts"
  }
}

Input Schema

Name	Required	Description
`featured`	No	Filter featured posts only
`topic`	No	Filter by topic slug
`postedAfter`	No	Filter after date (ISO 8601)
`postedBefore`	No	Filter before date (ISO 8601)
`order`	No	Order: FEATURED_AT, NEWEST, RANKING, VOTES
`first`	No	Number of posts (default: 10, max: 20)
`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

C2.8/5.0

Behavior2/5

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

Absent annotations, the description only mentions 'returns cleaned data in TOON format', lacking disclosure of read-only nature, permissions, or side effects.

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?

Two sentences, no waste, but overly brief; misses key contextual elements that could be included without verbosity.

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?

With 9 parameters, no output schema, and no annotations, the description is insufficient for an agent to understand pagination, defaults like 'first' vs 'max_items', or error handling.

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 covers 100% of parameters, so baseline 3 applies; description adds no extra parameter meaning beyond schema.

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 clearly states the verb 'Get' and resource 'Product Hunt posts' with filters, but does not differentiate from sibling tools like 'get_post' or 'search_posts'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no exclusion criteria or when-not-to-use hints.

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

Deploy Server