Skip to main content
Glama

Product Hunt collection products

run_producthunt_collections
Read-onlyIdempotent

Products of a Product Hunt collection in the curator's order, with the full list paged beyond the first 20. 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": {
      "collection": "<collection>"
    },
    "name": "run_producthunt_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_itemsNoMax items (up to 250) Default: 25.
collectionYesCollection slug or Product Hunt URL. e.g. 0-design-tools
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered structurally. The description adds genuinely new context beyond that: results are in the curator's order, the endpoint pages past the first 20 records, and each returned record costs 1 point. Ordering, pagination depth, and credit cost are exactly the behavioral facts annotations cannot express.

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 the resource and ordering stated first, followed by pagination and cost. Nothing is wasted and the key scoping fact is front-loaded. The middle clause ('with the full list paged beyond the first 20') is slightly awkward but still earns its place.

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 collection-listing tool with a fully documented 3-param schema and no output schema, the description covers what matters: scope, ordering, pagination, and cost. It could say a little more about record shape or paging limits, but no output schema exists and the safety profile is carried by annotations, so it is nearly complete.

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 collection, max_items, and start_page are already documented in the schema, making 3 the baseline. The description reinforces the start_page semantics ('paged beyond the first 20') and insinuates that record count drives cost, but adds no format or syntax detail beyond what the schema provides.

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 and scope: the products belonging to a Product Hunt collection, returned in the curator's order. Combined with the title, an agent can tell this apart from generic search tools at a conceptual level. It does not, however, name or distinguish itself from the close siblings run_producthunt_collections_search or run_producthunt_users_collections, so it lands at 4 rather than 5.

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?

Usage is only implied: the note that the list is 'paged beyond the first 20' signals this is the retrieval call for a full collection, and '1 point per returned record' hints that cost scales with volume, nudging the caller to set max_items deliberately. There is no explicit when-to-use/when-not, no prerequisites, and no named alternative for collection discovery. Adequate but with clear gaps.

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