Skip to main content
Glama

run_producthunt_launches_search

Search Product Hunt launches by keyword to retrieve each launch's name, date, and underlying product for research.

Instructions

Search Product Hunt launches by keyword: name, date and the product behind each launch. 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_launches_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.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add one useful fact, the '1 point per returned record' cost signal, but says nothing about pagination behavior, result granularity, or permissions/auth needs for a search that supports start_page and max_items.

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 the resource and scope front-loaded, and the cost note is genuinely useful rather than filler. Nothing is wasted.

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?

There is no output schema, and the description partially compensates by naming the returned fields. However, with no annotations, no alternative routing, and no mention of paging behavior for a paginated search, the definition is only minimally adequate for the surrounding Product Hunt tool family.

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 the schema already documents keyword, max_items, and start_page fully, including the 250 cap. The description only restates the keyword dimension and adds no syntax, defaults, or paging semantics beyond what structured data already conveys.

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 and resource ('Search Product Hunt launches by keyword') and even enumerates the fields returned (name, date, product). It is clearly a keyword search rather than a listing, but it does not name or contrast with the sibling run_producthunt_launches, so an agent must infer the distinction.

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 gives no when-to-use, when-not-to-use, or alternative routing guidance. With run_producthunt_launches, run_producthunt_products_launches, and run_producthunt_products_search all present, there is no signal telling the agent which one to pick.

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