Product Hunt MCP Server

get_post_comments

Fetch comments for a Product Hunt post. Returns cleaned data with options for ordering (newest or votes) and pagination.

Instructions

Get comments on a post. 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_post_comments"
  }
}

Input Schema

Name	Required	Description
`postId`	No	Post ID
`postSlug`	No	Post slug
`order`	No	Order: NEWEST, VOTES
`first`	No	Number to return (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

B3.1/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden. It only mentions 'Returns cleaned data in TOON format,' but does not disclose pagination behavior, required identifiers, or any safety considerations. Critical behavioral traits are missing.

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 sentences with no wasted words. However, it could be slightly more informative without sacrificing 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 7 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain parameter choices (postId vs postSlug), pagination, or the meaning of 'cleaned data.'

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 additional meaning to parameters beyond what the schema already provides (e.g., postId, order, pagination).

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 clearly states 'Get comments on a post,' specifying the verb and resource. This differentiates it from siblings like 'get_comment' (single comment) and 'get_post' (post details).

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. The description does not mention prerequisites, context, or conditions for use. The agent is left to infer usage from the name alone.

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

Deploy Server