Skip to main content
Glama

Launch a product on RankRoot

submit_launch
Idempotent

Launch the user's product on RankRoot for free: a public launch page, a listing in the launch directory and the product's category, and a count of visitors sent. Free launches go live in about a week after the user confirms by email. With a Launch Kit license key (key) it goes live today and is featured for 30 days. Ask the user before submitting: it publishes their product publicly.

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": {
      "url": "<url>",
      "name": "<name>",
      "tagline": "<tagline>",
      "description": "<description>",
      "email": "<email>"
    },
    "name": "submit_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional Launch Kit license key
urlYesProduct website
nameYes
emailYesFounder's email for the confirmation link; never shown
taglineYes10-90 characters: what it does, for whom
categoryNoIndustry slug, or other
descriptionYes40-800 characters, written for buyers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / key / description
      Previous value: -"Optional Traffic Boost license key"New value: +"Optional Launch Kit license key"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: public publication, email confirmation gating, a roughly one-week free moderation delay versus same-day live with featured placement for 30 days, and a consent requirement. One gap remains — the annotations declare idempotentHint=true, but the description never says whether resubmitting the same URL updates an existing launch or creates a duplicate.

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?

Four tight sentences: what you get, the free path, the licensed path, and the consent rule — with the highest-stakes constraint (public publishing, ask first) placed last as a clear imperative. No filler or restated title.

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?

No output schema exists, and the description does not state what the tool returns on success (a launch URL, an identifier, or a pending-status confirmation), which an agent needs to report back to the user. Everything about inputs, timing, and consent is otherwise complete for a 5-required-parameter submission tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3, but the description adds real meaning beyond the schema for 'key' by explaining that it changes timing (live today) and placement (30-day feature), and for 'email' by noting the confirmation link flow. It says nothing extra about category slug conventions or character-count limits that the schema already covers.

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 (launch the user's product on RankRoot) and enumerates exactly what the launch produces: a public launch page, a listing in the directory and category, and a visitor count. It is trivially distinguishable from siblings like list_launches or get_pricing.

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 clear selection logic between the free path (goes live in about a week after email confirmation) and the licensed path with a Launch Kit key (live today, featured 30 days), plus an explicit consent instruction: 'Ask the user before submitting.' It does not point at siblings such as list_launches for checking status or get_pricing for the paid tier, so it stops short of full alternative routing.

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