Skip to main content
Glama

run_indiehackers_products_search

Browse Indie Hackers products by sort, category, business model, and monthly revenue range to find names, taglines, and self-reported revenue.

Instructions

Browse the Indie Hackers products directory by sort, category, business model and monthly revenue range: name, tagline and self-reported revenue. 1 point per returned record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_indiehackers_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort. Options: recently-updated = Recently updated, recently-added = Recently added, highest-revenue = Revenue: high to low, lowest-revenue = Revenue: low to high
categoryNoCategory slug. e.g. ai
max_itemsNoMax items (up to 18)
business_modelNoBusiness model. Options: free = Free, ads = Advertising, commission = Affiliate / commission, transactions = Transactional, subscriptions = Subscription-based
monthly_revenue_maxNoMonthly revenue to (USD)
monthly_revenue_minNoMonthly revenue from (USD)

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. It does add genuine behavioral value by disclosing the returned fields and the cost ('1 point per returned record'), but it omits the 18-item cap, pagination behavior, and any auth requirements.

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?

Purpose and filters are front-loaded in one dense sentence, with the cost caveat isolated as a short trailing sentence. No filler, though the single long clause is slightly dense.

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 6-parameter, fully-optional browse tool with no output schema and no annotations, the description covers purpose, filters, return fields, and cost. It lacks the max-item cap and pagination notes, which is the main remaining 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 coverage is 100%, so all six parameters are already documented in the schema. The description restates the filter dimensions and adds the qualifier 'self-reported' for revenue, which adds slight meaning, but otherwise does not enrich the schema's enum explanations or bounds.

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 (Browse) and resource (Indie Hackers products directory) plus the exact filter dimensions and returned fields, so an agent knows what it gets. It does not explicitly differentiate itself from the sibling run_indiehackers_products (single-record fetch) or the other indiehackers search tools, which keeps it from a 5.

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 when-to-use, when-not, or alternative guidance is given. The filter list implies a browse/search pattern, but nothing tells the agent to prefer this over run_indiehackers_products or run_indiehackers_ideas_search.

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