Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Product Hunt product

product_hunt_product_get
Read-onlyIdempotent

Fetch a Product Hunt product by slug to retrieve its website, rating, reviews, followers, and latest launch details for research or comparison.

Instructions

Get one Product Hunt product by slug: website, rating, reviews, followers and latest launch. 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_product_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Product slug, e.g. `notion`; 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.6/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 adds the returned field set, but says nothing about behavior on an unknown slug, rate limits, or response shape beyond the field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the resource, the lookup key, and the payload contents; no filler and nothing buried.

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, listing the returned fields is valuable and mostly sufficient for a simple single-record getter. Only error handling for a missing/invalid slug is left unaddressed, and the schema's pattern and maxLength partly cover that.

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 `slug`, `context`, `llm_model` and `conversation_id` are fully documented in the schema. The description only repeats that `slug` is required, adding no syntax or format detail beyond what the schema provides.

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 (get one Product Hunt product by slug) and enumerates what is returned: website, rating, reviews, followers, latest launch. That field list distinguishes it from post/topic/review siblings, though no alternative is named 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?

Usage is only implied by "by slug" and a bare "Requires `slug`". There is no explicit when-to-use, when-not, or pointer to siblings like product_hunt_post_get or product_hunt_product_reviews_list for adjacent data.

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