Skip to main content
Glama

Product Hunt topic products

run_producthunt_topics
Read-onlyIdempotent

Products of a Product Hunt topic: name, tagline, rating, review count, launches and categories. 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": {
      "topic": "<topic>"
    },
    "name": "run_producthunt_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic slug or Product Hunt URL. e.g. artificial-intelligence
max_itemsNoMax items (up to 250) Default: 25.
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the cost model ('1 point per returned record'), which an agent needs for budgeting calls. It does not detail pagination or error behavior, which keeps it below 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 short sentences: the first front-loads the resource and returned fields, the second states the credit cost. No filler or repetition.

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 read-only list tool with no output schema, the description adequately covers what comes back by listing the fields (name, tagline, rating, review count, launches, categories) and the cost. Minor gaps like pagination behavior or ordering are not addressed but are not critical.

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 topic slug/URL format, max_items default and 250 cap, and start_page are all documented in the schema itself. The description adds no parameter-level detail, so the baseline 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?

The description states a specific resource (products of a Product Hunt topic) and enumerates the returned fields, which distinguishes it from run_producthunt_products (single product) and run_producthunt_launches. It does not explicitly name a sibling to contrast with, so it falls just short of the top band.

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 guidance on when to use this tool versus alternatives such as run_producthunt_products_search or run_betalist_topics_startups. The usage is only implied by the resource description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources