Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List most-active Product Hunt posts

product_hunt_posts_list
Read-onlyIdempotent

Fetches current most-active public Product Hunt posts, optionally filtered by a topic slug, so you can track trending products and discussions across all topics or one niche.

Instructions

List the current most-active public Product Hunt posts, optionally filtered by one topic slug. Optional inputs: topic. Returns a list.

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_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic slug to filter the most-active list by, e.g. `artificial-intelligence`; case does not matter. Unknown values return `not_found`. Omit for the list across all topics.
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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without the description. The description adds the 'public' scope and 'Returns a list', but leaves unexplained what 'most-active' measures and over what window, which is the one behavioral fact a caller actually needs.

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 the resource and scope. 'Optional inputs: `topic`' is mildly redundant with the preceding 'optionally filtered by one topic slug', a small trimming opportunity rather than a real flaw.

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

Completeness3/5

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

Rich schema coverage and full annotations mean much of the burden is elsewhere, but for a ranking-style feed the description never defines 'most-active' or 'current', leaving an agent unable to predict or explain what the list contains. Adequate to invoke, incomplete to interpret.

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 the schema already documents `topic` including its example, case-insensitivity, and the `not_found` behavior for unknown values, as well as the context/llm_model/conversation_id plumbing. The description only restates the single filter and adds no format or syntax detail beyond it, so 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 ... public Product Hunt posts') with a distinguishing qualifier ('most-active') and an optional scope ('filtered by one topic slug'). It does not name the sibling tools (e.g. product_hunt_topic_posts_list, product_hunt_launches_list) that a caller might confuse it with, so it stops short of a 5.

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?

The only guidance is that a topic slug may optionally be supplied; there is no statement of when this list is the right choice versus the topic/user/launches lists in the sibling set, and no exclusions. The 'omit for all topics' hint lives in the schema, not the description, so the description itself offers no routing help.

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