Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt topics

product_hunt_topics_list
Read-onlyIdempotent

Lists Product Hunt topics with cursor-based pagination so you can browse categories, discover communities, and page through up to 100 topics at a time.

Instructions

List Product Hunt topics, cursor-paged, with up to 100 topics per page. Optional inputs: cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "product_hunt_topics_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds the page-size ceiling of 100 and the cursor-paging behavior, which is useful beyond the annotations, but says nothing about result ordering or rate limits.

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 with the resource and pagination scope front-loaded and no filler. The closing "Returns a list (use cursor when paginated)" is slightly redundant with the opening clause, which keeps it from a 5.

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

Completeness5/5

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

This is a simple read-only list tool with a fully documented four-parameter schema and complete safety annotations, and no output schema is needed since the return shape (a list of topics plus a next cursor) is stated. Everything an agent needs to call it correctly is present.

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%, and the schema already explains that cursor comes from `page.nextCursor` of the previous response and only works with the same endpoint and filters. The description merely restates that `cursor` is optional, adding no syntax or constraint detail beyond the schema; baseline 3 applies.

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 Product Hunt topics") plus the pagination shape and page-size cap, which lets an agent distinguish it from the singular product_hunt_topic_get. It stops short of naming any sibling explicitly, so differentiation relies on inference from the name.

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 parenthetical "use cursor when paginated" gives a concrete instruction for continuing through results, which is real usage guidance. However, there is no statement about when to choose this over product_hunt_topic_get or product_hunt_topic_posts_list, and no exclusions.

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