Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt post comments

product_hunt_post_comments_list
Read-onlyIdempotent

Lists cursor-paged comments for a Product Hunt post by slug, including the first 20 replies per thread, enabling discussion review across pages.

Instructions

List Product Hunt post comments, cursor-paged, with the first 20 replies on each thread. Requires slug. 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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "product_hunt_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Post slug, e.g. `teamily-ai`; case does not matter.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same endpoint and filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe 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_idNoEcho 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value annotations cannot: results are cursor-paged and only the first 20 replies per thread come back, which warns the agent that the payload is truncated rather than exhaustive. It stops short of ordering, rate limits, or whether deeper replies are reachable via another call.

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?

Two short sentences, front-loaded with purpose and the key truncation caveat, with no filler. Minor redundancy between 'cursor-paged' and 'use cursor when paginated', and 'Returns a list' restates the verb in the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of return-value disclosure and does convey that output is a list plus the 20-replies-per-thread limit. It omits whether the pagination reflects threads or replies and what fields each comment carries, a small gap for a list tool with five parameters.

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 `slug`, `cursor`, `context`, `llm_model`, and `conversation_id` are all documented in the schema itself. The description only echoes the `slug` requirement and cursor usage already covered there, adding no new format or constraint detail, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('List Product Hunt post comments') scoped to a named platform, which cleanly separates it from the many other `*_post_comments_list` siblings in the catalog. An agent can identify what it retrieves without opening the schema.

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 implies usage by stating 'Requires `slug`' and 'use cursor when paginated', which tells the agent the minimum to call it. It gives no explicit when-to-use/when-not guidance relative to alternatives such as `product_hunt_post_get` or the other comment-listing tools, leaving the agent to infer the selection rule.

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

Deploy Server

Other Tools