Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Product Hunt topic

product_hunt_topic_get
Read-onlyIdempotent

Retrieve a Product Hunt topic by slug to view its name, description, and follower count for research or audience insights.

Instructions

Get one Product Hunt topic by slug: name, description and follower count. Requires slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Topic slug, e.g. `artificial-intelligence`; case does not matter.
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
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's only added behavioral value is the shape of the returned record, which partially compensates for the absent output schema; it says nothing about lookup failures or unknown slugs.

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?

A single front-loaded sentence with the resource first and the return fields second — efficient and easy to scan. The trailing 'Requires `slug`' lightly duplicates the schema's required array.

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 simple read-only lookup with full annotation coverage and no output schema, the description supplies enough: verb, keying parameter, and return fields. Missing only minor details such as behavior for a nonexistent slug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description restates the key semantic constraint (slug required, single-resource lookup) rather than contradicting the schema. It adds little beyond the schema's own 'case does not matter' and pattern details, so it stays near baseline.

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 ('Get one Product Hunt topic by slug') and enumerates the returned fields (name, description, follower count). The singular 'one ... by slug' framing makes it clearly distinct from a topics-list sibling.

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?

Usage is only implied: fetch a single topic when you already have its slug. There is no explicit when-to-use/when-not-to-use statement and no pointer to a list/search tool for discovering a slug you don't have.

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