Skip to main content
Glama

Launchator

Submit a product

submit_product

Start a free Launchator listing for the user's own website, or for one product's page on a site with several products (up to 3 per website). Loads the page, screens it, and drafts the listing (takes about 30 seconds). Returns the draft and the next step. Needs an access token.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe product's homepage or its own page, e.g. https://example.com or https://example.com/apps/name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"The product's homepage, e.g. https://example.com"New value: +"The product's homepage or its own page, e.g. https://example.com or https://example.com/apps/name"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the external page load and screening, the ~30 second runtime, the fact that a draft — not a published listing — is produced, and that an access token is required. That is substantial behavioral context; it does not cover what happens when screening fails.

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 short sentences, front-loaded with the action and scope, followed by runtime, return shape, and auth in descending order of importance. No filler and nothing redundant with the schema.

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 single-parameter tool with no output schema, the description covers scope, cost (30s), side effect (a draft is created), return value, and auth. It leaves the 'next step' vague and says nothing about screening failure paths, which keeps it from a 5.

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 100% so the URL format is already documented. The description still adds real constraint beyond the schema by stating the URL must be the user's own site or a single product page, which governs which URLs are valid inputs.

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?

The description names a specific action and resource ('Start a free Launchator listing') and disambiguates the two legitimate targets: the user's own website or one product page on a multi-product site. It does not explicitly contrast with close siblings such as publish or update_listing, so a 4 rather than 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 Guidelines4/5

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

It gives clear conditions for use (own website, or a single product page, with a stated 'up to 3 per website' cap) and implies the flow ends in a draft that requires a next step. It stops short of naming the follow-up tool or telling the agent what to do when a listing already exists.

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