Skip to main content
Glama

List launches

list_launches
Read-onlyIdempotent

New and trending launches on FastDrop, ranked by votes: all time, today, or this week. Use when the user asks what's new or trending in AI tools, MCP servers, or indie software, or what people launched today or this week. Each product may include an MCP endpoint URL, mcpVerified (whether FastDrop's probe succeeded), and mcpAuthRequired when the endpoint answered 401/403.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, 1-50, default 20
windowNoRank by votes cast in this window (UTC). Default all-time.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. 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"
      +}
  3. First observed

TDQS

A4.3/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. The description adds real value beyond them by explaining the response fields that carry non-obvious meaning: MCP endpoint URL, mcpVerified (probe success), and mcpAuthRequired when the endpoint returned 401/403. This tells the agent how to interpret ambiguous results, which annotations cannot. It omits pagination/ordering edge cases, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences: what it is, when to use it, what comes back. Ranking scopes are front-loaded ahead of usage guidance, and no sentence is filler.

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 an output schema present, the description need not explain return structure, and it still flags the interpretation-critical fields. Filters, defaults, and intent mapping are all covered for a two-parameter, no-required-args read tool.

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%, with limit (1-50, default 20) and window (enum, UTC, default all) fully documented in the schema. The description largely restates the window options and ranking basis without adding format or interaction detail, so the baseline 3 applies.

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?

States a specific verb and resource (list launches) plus the ranking basis (votes) and available scopes (all time, today, this week). An agent can distinguish this from siblings like search_products or get_engagement_feed, which are retrieval by query/feed rather than ranked launch listings.

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

Usage Guidelines4/5

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

Gives an explicit use context: 'Use when the user asks what's new or trending in AI tools, MCP servers, or indie software, or what people launched today or this week.' That maps intent to window values, which is genuinely helpful. It does not name alternatives (e.g. search_products for keyword lookup) or state exclusions, so it stops short of a 5.

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