Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

producthunt_about

Retrieve a Product Hunt product's about page by slug to get launch details, badges, ranks, comments, reviews, alternatives, ads, forum, and media data in one JSON response.

Instructions

Retrieve Product Hunt product about page. Returns the about-page data for a Product Hunt product, looked up by its slug in id. It covers the product's launch details with badges, ranks, comment count and detailed reviews with alternative products, along with the product's ad, forum and media information.

Input Schema

NameRequiredDescriptionDefault
idYesProduct Hunt slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does a good job disclosing the returned payload (launch details, badges, ranks, comment count, reviews with alternatives, ad/forum/media info). 'Retrieve' makes the read-only nature clear. It stops short of covering auth, rate limits, or pagination, so it is strong but not exhaustive.

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?

Two sentences, front-loaded with the purpose and the lookup mechanism before the content inventory. The second sentence is a long enumerative list but every item conveys what the agent will receive, so little is 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 single-parameter, fully-documented lookup tool with no output schema, the description compensates well by enumerating the returned data. The main remaining gap is the absence of any routing guidance among the many producthunt_* siblings.

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% (the `id` property is documented as 'Product Hunt slug'), so the schema already does the heavy lifting. The description reinforces that `id` is the slug used for lookup but adds no new syntax or format detail, matching the baseline 3.

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 ('Retrieve Product Hunt product about page') and explains the lookup key ('slug in `id`'). The purpose is clear, but the description never differentiates this about-page tool from close siblings like producthunt_product, producthunt_reviews, or producthunt_alternatives, which appear to overlap with the listed contents.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. The agent is told what the tool returns but not when to prefer it over the sibling producthunt_product or producthunt_reviews tools.

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