Skip to main content
Glama

run_producthunt_products_customers

Retrieve customers of a Product Hunt product, including shoutout notes, by product slug or URL. Use it to page through up to 250 records for outreach or research.

Instructions

Customers of a Product Hunt product (products whose makers say they use it) with the shoutout note. 1 point per returned record.

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": {
      "product": "<product>"
    },
    "name": "run_producthunt_products_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct slug or Product Hunt URL. e.g. notion
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a genuine behavioral trait not present in structured data – the cost of '1 point per returned record' – but says nothing about pagination behavior, permissions, or the shape of the response.

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 short sentences with no wasted words, and the resource definition is front-loaded. The trailing cost note is a distinct concern appended after the core statement, which slightly dilutes the focus.

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?

For a simple three-parameter retrieval tool with full schema coverage and no output schema, the description covers what is returned and the cost. It omits pagination guidance, which matters given the max_items/start_page parameters, leaving a modest 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 product, max_items, and start_page are already documented in the schema (including the 250 cap and example slug). The description adds no additional parameter meaning, 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?

States a specific resource – the customers of a Product Hunt product – and disambiguates the term with 'products whose makers say they use it'. This is enough to separate it from sibling tools like run_producthunt_products_reviews or run_producthunt_products_alternatives, though the retrieval verb is only implied.

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?

No indication of when to use this tool versus the many other run_producthunt_* tools, and no prerequisites or exclusions. The agent is left to infer usage from the name alone.

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