Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Product Hunt post

product_hunt_post_get
Read-onlyIdempotent

Fetch a Product Hunt post by slug to retrieve votes, rank, comments, pricing, topics, and linked product details for research or comparison.

Instructions

Get one Product Hunt post by slug: votes, ranks, comments, pricing, topics and the linked product. 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_post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Post slug, e.g. `teamily-ai`; 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.5/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 without the description. The description adds the useful fact that a single record is returned and which field groups it contains, but says nothing about missing-slug behavior, rate limits, or auth requirements.

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 that puts the identity and scope first, then the payload contents. The trailing "Requires `slug`" is mildly redundant with the schema's own "Required" label but is short enough not to be wasteful.

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, the description usefully enumerates the returned facets (votes, ranks, comments, pricing, topics, linked product) so an agent knows whether this call answers the question. It is complete for a simple single-record read, with only missing-slug behavior and the comments-vs-comments_list boundary left unaddressed.

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%, with each of the four parameters already documented, including slug's pattern and required status. The description's "Requires `slug`" merely restates the schema and adds no format or edge-case detail, so the baseline of 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?

The description names a specific verb and resource ("Get one Product Hunt post by slug") and enumerates what the record contains: votes, ranks, comments, pricing, topics, and the linked product. The scoping word "one" implicitly separates it from the list-style siblings like product_hunt_posts_list, but no sibling is named explicitly, so it falls short of the top tier.

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 implied by the description: this is the tool for a single post when you already know the slug. There is no explicit when-to-use/when-not guidance, no mention of when to prefer product_hunt_product_get for the linked product, and no note on error behavior for a slug that does not exist.

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