Skip to main content
Glama

run_producthunt_products_search

Search Product Hunt products by keyword to retrieve names, taglines, ratings, review counts, logos, and links for market or competitor research.

Instructions

Search Product Hunt products by keyword: name, tagline, rating, review count, logo and link. 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": {
      "keyword": "<keyword>"
    },
    "name": "run_producthunt_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword. e.g. crm
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?

With no annotations, the description carries the full burden, and it does add one genuine behavioral fact: '1 point per returned record', a cost signal that helps the agent budget calls. It also discloses the return fields, partially compensating for the absent output schema. However, it omits result ordering, pagination semantics, and any rate/permission context.

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 compact sentences, the primary purpose front-loaded, and the cost note placed last. Every element earns its place, with no rephrasing of the title or filler.

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 three-parameter search tool with no output schema, the description usefully enumerates the returned record fields and flags per-record cost, which is exactly the information the missing output schema would otherwise supply. It is adequate for correct invocation, with only the when-to-use routing gap remaining.

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% – keyword, max_items (1-250), and start_page are all documented in the schema. The description adds no parameter-level detail beyond restating the keyword-first model, so the baseline 3 applies; the structured fields do the work here.

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 (Search) plus resource (Product Hunt products) and the input mode (by keyword), so the agent can tell this apart from retrieval-style siblings like run_producthunt_products. It also enumerates the returned fields (name, tagline, rating, review count, logo, link), which sharpens what the tool yields. It does not explicitly contrast itself with the many sibling search tools, but the purpose is unambiguous.

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?

The description implies keyword-driven usage but gives no explicit when-to-use guidance, no prerequisites, and never names an alternative (e.g. run_producthunt_products vs run_producthunt_products_search). The only supplementary cue is the cost note, which is not usage routing. An agent must infer selection 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