Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

producthunt_product

Retrieve core Product Hunt product details by slug or numeric ID. Use a known slug; if you only have a product name, search for its slug first to avoid 404 errors.

Instructions

Retrieve Product Hunt product details. Returns the core Product Hunt product details. The path takes an exact Product Hunt slug; if you only know the product name, look the slug up first with /producthunt/search (live) or /datasets/producthunt-products/search (indexed). Unknown slugs return 404, and that 404 is cached for 24 hours.

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": {
      "id": "<id>"
    },
    "name": "producthunt_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct Hunt slug or numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that unknown slugs return 404 and that those 404s are cached for 24 hours, but it does not describe authentication, rate limits, return shape, or confirm read-only semantics beyond the word 'Retrieve'.

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?

The description is short and front-loads the action and resource. The second sentence, 'Returns the core Product Hunt product details,' is largely redundant with the first, but the remaining lookup and 404-caching details are useful and efficiently stated.

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 one-parameter read tool with no output schema, the description covers how to supply the identifier, where to find a slug if needed, and what happens on an unknown input. It is slightly incomplete on what 'core details' actually includes and does not reconcile the slug-only phrasing with the schema's numeric ID support.

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 the single 'id' parameter as 'Product Hunt slug or numeric ID'; the baseline is therefore 3. The description adds that the path takes an exact slug, which helps, but it omits the schema-supported numeric ID case and could mislead an agent into assuming only slugs are accepted.

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 states a specific verb and resource: 'Retrieve Product Hunt product details' and clarifies it returns core product details. It also distinguishes this from name-based lookup by pointing to search tools, though it does not fully differentiate itself from other product-adjacent siblings such as reviews or makers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives a clear prerequisite and alternative path: the tool requires an exact slug, and agents should use /producthunt/search or /datasets/producthunt-products/search if they only know the product name. It does not explain when to prefer this live detail tool versus the indexed dataset item tool, but the main lookup guidance is explicit.

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