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.

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

Input Schema

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

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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are vote-ranked within a UTC window, and items may carry an MCP endpoint plus mcpVerified and mcpAuthRequired, with the latter specifically meaning the endpoint answered 401/403. It does not discuss pagination or result caps, which keeps it out of 5 territory.

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?

Three sentences, front-loaded with the purpose and the usage trigger, with the return-field detail last where it belongs. Every sentence carries information, though the MCP-field sentence is somewhat dense relative to an output schema that presumably already defines those fields.

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?

Purpose, trigger conditions and notable return fields are all covered, and an output schema exists to carry the response shape, so an agent has what it needs to call this correctly. The only real omission is guidance on choosing this over sibling discovery tools such as search_products or find_tools.

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 both the limit range (1-50, default 20) and the window enum with its UTC/default semantics are already fully documented. The description restates the three window labels but adds no format or edge-case guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names the resource (launches on FastDrop), the ranking rule (by votes) and the scope options (all time, today, this week) in the first sentence. That is enough to separate it from keyword-oriented siblings like search_products and find_tools, and from get_engagement_feed, without opening a schema.

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?

It gives an explicit trigger: '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 is a clear when-to-use statement. It stops short of naming alternatives or exclusions (e.g. when to prefer search_products or find_tools instead), so it falls below 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