Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

producthunt_customers

Retrieve paginated customer lists for a Product Hunt product using its slug. Specify order by customers or latest launch, and control page size.

Instructions

Retrieve Product Hunt product customers. Returns paginated customer products for a Product Hunt product using Product Hunt's ProductCustomersPage GraphQL operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct Hunt slug
pageNoPage number
orderNoProduct Hunt customers order
page_sizeNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / order / enum
      Added value: +[
+  "customers",
+  "latest_launch"
+]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full transparency burden. It discloses that results are paginated and references Product Hunt's ProductCustomersPage GraphQL operation, but it does not explain what 'customer products' means, whether authentication is needed, or any rate-limit considerations.

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 no filler. The verb and resource are front-loaded, and the second sentence adds pagination and implementation context without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core behavior is covered: it retrieves paginated customer products for a product. However, the semantics of 'customer products' are ambiguous, and with no output schema, the return value shape is not further clarified. A sentence explaining what constitutes a customer product would improve completeness.

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% and all four parameters have clear descriptions in the schema. The description adds only the pagination context and does not provide additional per-parameter meaning, keeping this at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 customers.' It also specifies that results are paginated and names the underlying GraphQL operation, making the tool's purpose distinct from sibling Product Hunt tools like producthunt_reviews or producthunt_makers.

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?

The description makes clear that the tool is for retrieving customers for a Product Hunt product, but it does not explicitly contrast with alternatives or state when not to use it. Given the large family of Product Hunt sibling tools, explicit routing would have been valuable.

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