Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt topic posts

product_hunt_topic_posts_list
Read-onlyIdempotent

List posts from a Product Hunt topic with ordering, cursor pagination, and total counts. Retrieve topic posts to analyze rankings, trends, and engagement.

Instructions

List posts of one Product Hunt topic, ordered and cursor-paged, with the total count. 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_topic_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Topic slug, e.g. `artificial-intelligence`; case does not matter.
orderNoHow to order the posts: `VOTES` (default), `SCORE`, or one of the rank orders.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds useful behavior — ordering, cursor paging, and a total count in the response — but says nothing about rate limits, per-page limits, or what a post record contains.

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 compact sentences with the resource stated first and the pagination caveat last; there is no filler. The parenthetical "(use cursor when paginated)" is slightly redundant against the cursor field description but not wasteful enough to penalize further.

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 does carry the burden of explaining returns, and it does so at a coarse level (a list, a total count, cursor for paging). For a six-parameter list tool whose extra params are fully documented in schema, this is close to complete, though the shape of an individual post is unstated.

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 description coverage is 100%, so the enum values, slug pattern, and cursor provenance are all already documented in the schema. The description only restates that slug is required and that the cursor comes from a prior page, adding no meaning beyond the existing field descriptions.

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?

States a specific verb and resource ("List posts of one Product Hunt topic") plus the scope qualifier "one topic", which implicitly separates it from product_hunt_posts_list and product_hunt_user_posts_list. It stops short of naming the alternative sibling explicitly.

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?

Conveys the required input ("Requires `slug`") and the pagination rule ("use cursor when paginated"), so usage is inferable. It never states when to pick this over product_hunt_posts_list or the user-scoped variant, so the agent must reason about the substitution itself.

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