Product Hunt MCP Server

get_user_posts

Retrieve posts made by a Product Hunt user. Supports pagination and saves cleaned JSON data for further analysis.

Instructions

Get posts made by a user. 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": {
      "username": "<username>"
    },
    "name": "get_user_posts"
  }
}

Input Schema

Name	Required	Description
`username`	Yes	Username
`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 (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior. It implies a read operation but does not mention that the 'save_dir' parameter indicates a file-writing side effect, nor does it address auth or rate limits. Critical behavioral traits are omitted.

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 brief with two sentences, no redundancy. However, it could be more structured by front-loading the primary action and listing key nuances.

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 no output schema and no annotations, the description is insufficient. It does not explain pagination behavior (parameters 'first', 'after', 'max_items') or the file-saving side effect. The agent lacks a complete picture for safe usage.

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 baseline is 3. The description adds no further semantic context beyond what the schema already provides (e.g., 'cleaned data' and 'TOON format' are not linked to parameters).

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 tool retrieves posts made by a user, with a specific verb and resource. It also mentions return format ('cleaned data in TOON format'). However, it does not explicitly differentiate from sibling tools like 'get_posts' or 'get_user_voted_posts', which reduces clarity.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or constraints. Agents receive no context for appropriate invocation.

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

Deploy Server