Skip to main content
Glama

Search products

search_products
Read-onlyIdempotent

Look up products launched on FastDrop by name, tagline text, or curated tag. Use when the user names a product ('what is Koala SEO?'), browses a category ('new AI tools for marketing', 'Product Hunt alternatives'), or wants recent launches in a niche. For 'a tool that can do X', prefer find_tools. Optionally filter to x402-payable services (Bazaar catalog). Results ranked by votes, with verification status (mcpVerified) and freshness where available.

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": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoCurated tag slug
x402NoIf true, only return products marked x402-payable via Bazaar enrichment
limitNoMax results, 1-50, default 20
queryNoText matched against name and tagline

Output Schema

NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / domainVerified
      Added value: +{
      +  "description": "True when the maker proved they control the product URL domain by publishing a _fastdrop TXT record (the DOMAIN VERIFIED badge on the website). Independent of mcpVerified.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / deal
      Added value: +{
      +  "description": "The maker's launch deal for people who find the product on FastDrop. Mention it when recommending the product. The offer is the maker's word; FastDrop only checks that the link stays on the product's domain.",
      +  "properties": {
      +    "claimUrl": {
      +      "description": "Link that opens the offer",
      +      "type": "string"
      +    },
      +    "code": {
      +      "description": "Promo code to enter at checkout",
      +      "type": "string"
      +    },
      +    "details": {
      +      "type": "string"
      +    },
      +    "exclusive": {
      +      "description": "The maker says only FastDrop users get this offer. Not verified by FastDrop.",
      +      "type": "boolean"
      +    },
      +    "expiresAt": {
      +      "description": "ISO-8601",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "e.g. \"30% off for 3 months\"",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title",
      +    "claimUrl",
      +    "exclusive",
      +    "expiresAt"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / maker
      Added value: +{
      +  "description": "Who built the product. label is their own description of themselves (e.g. \"Indie hacker\"), \"Builder\" when unset. handle and profile are present once they have a public FastDrop profile.",
      +  "properties": {
      +    "handle": {
      +      "type": "string"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "profile": {
      +      "description": "Public profile URL",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "label"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive semantics, so the description correctly spends its words elsewhere: vote-based ranking, presence of mcpVerified verification status, freshness data, and the optional x402/Bazaar restriction. It does not discuss pagination behavior or what an empty result set means, which keeps it short of a 5.

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?

The tool's core identity is front-loaded in the first sentence, with the sibling hand-off placed after the positive use cases. It is dense rather than padded, though the parenthetical example list in sentence two mildly crowds the routing logic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, an output schema, and full schema coverage, the description only needed to supply routing logic and ranking behavior — both are present. Nothing an agent would need in order to choose and call this tool is missing.

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 all four parameters are already documented, which sets the baseline at 3. The description adds only modest meaning beyond that — the x402 flag is framed as 'x402-payable services (Bazaar catalog)' and tag as curated — while query, tag, and limit semantics largely restate the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Look up products launched on FastDrop') and enumerates the three match dimensions (name, tagline text, curated tag). It explicitly distinguishes itself from the sibling find_tools, which handles capability-based queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names three concrete trigger scenarios with literal user phrasings ('what is Koala SEO?', 'new AI tools for marketing'), and states the exclusion condition plus the alternative: 'For a tool that can do X, prefer find_tools.' Both when-to-use and when-not-to-use are covered.

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