Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Product Hunt category

product_hunt_category_get
Read-onlyIdempotent

Retrieve a Product Hunt category with its subcategories and cursor-paged product list by passing a category slug. Use it to browse products grouped by category and page through results.

Instructions

Get one Product Hunt product category with its subcategories and a cursor-paged product list. 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_category_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Category slug, e.g. `design-creative`; case does not matter.
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.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds real behavioral value by disclosing the response shape (subcategories plus a cursor-paged product list), which matters because no output schema exists. It does not mention rate limits or auth, keeping it below a 5.

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?

Two tight sentences with the resource and payload scope front-loaded and the required parameter called out last. Nothing is redundant or wasted.

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 single-resource fetch with a fully documented schema and no output schema, the description supplies what the agent needs: what is returned and that pagination exists. It omits error behavior (e.g., unknown slug) and whether the product list is filtered or sorted, leaving a small gap.

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 the schema already documents slug, cursor, and the context/llm_model/conversation_id conventions in detail. The description only restates that slug is required and hints at pagination via 'cursor-paged'; it adds essentially no syntax or constraint detail beyond structured data, matching the baseline.

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 uses a specific verb and resource ('Get one Product Hunt product category') and scopes the payload ('with its subcategories and a cursor-paged product list'), which clearly separates it from list-style siblings such as product_hunt_topics_list. It does not explicitly name an alternative, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the single-category fetch keyed by slug, versus the list endpoints implied by sibling names. There is no explicit when-to-use/when-not-to-use statement or named alternative, so it is minimum viable rather than instructive.

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