Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Product Hunt user posts

product_hunt_user_posts_list
Read-onlyIdempotent

List a Product Hunt user's made, submitted, or voted posts with cursor-based pagination to page through results.

Instructions

List a Product Hunt user's made, submitted or voted posts, cursor-paged. Requires username and kind. 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": {
      "username": "<username>",
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "product_hunt_user_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesRequired. Which list to page: `made`, `submitted` or `voted`.
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.
usernameYesRequired. Product Hunt username, e.g. `rrhoover`.
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.7/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 safety is covered. The description adds the cursor-paged nature of the results, which is useful beyond the annotations, but says nothing about rate limits, result ordering, or page size 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 no wasted words, and the resource and required-parameter constraint are front-loaded. It stops just short of being fully self-contained because the pagination clause is parenthetical rather than a clear instruction.

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?

For a read-only, six-parameter list tool with no output schema, the description covers what it returns ('a list') and how paging continues. The gaps (ordering, result envelope shape) are minor since read-only annotations and full schema coverage handle the rest.

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%, including the enum values for kind and cursor provenance ('page.nextCursor'), so the schema carries the semantic load. The description only restates that username and kind are required and echoes the cursor hint, adding no meaning beyond the structured fields.

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 (List), a scoped resource (a Product Hunt user's posts) and enumerates the three list kinds (made, submitted, voted). The 'user's' scoping distinguishes it from the generic product_hunt_posts_list sibling without needing 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?

Gives an in-call pagination hint ('use cursor when paginated') and states required parameters, but offers no when-to-use framing versus alternatives such as product_hunt_user_get or product_hunt_posts_list, and no when-not conditions. Usage is only implied.

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