Launchelion

Create a checkout link for a paid add-on

create_checkout

Create a Stripe checkout URL for one paid add-on on one listing, and return it for a HUMAN to open. Never present this as a completed purchase: nothing is charged until a person completes checkout in a browser. Returns an error when the listing doesn't exist, the add-on isn't purchasable yet (free early access), or payments aren't configured in this environment.

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": {
      "slug": "<slug>",
      "product": "<product>"
    },
    "name": "create_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer').
`product`	Yes	Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices.

Output Schema

Name	Required	Description
`ok`	Yes
`error`	No
`checkoutUrl`	No	A URL a HUMAN must open. Nothing is charged until a person completes it.
`instruction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 23, 2026

changedInput schema / properties / product / description

Previous value: -"Add-on key: premium_launch, review_one, review_monthly. See list_offers for names, effects, and prices."New value: +"Add-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices."

changedInput schema / properties / product / enum

Previous value: -[
-  "premium_launch",
-  "review_one",
-  "review_monthly"
-]New value: +[
+  "premium_launch",
+  "review_one",
+  "review_monthly",
+  "network_all",
+  "network_three"
+]

Changed1 schema field changedAug 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "checkoutUrl": {
+      "description": "A URL a HUMAN must open. Nothing is charged until a person completes it.",
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "instruction": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 20, 2026

changedInput schema / properties / slug / description

Previous value: -"The listing's slug (as in a toolUrl, e.g. '/tools/skillselion' -> 'skillselion')."New value: +"The listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer')."

First observedAug 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description adds essential behavioral details: checkout is not completed until a person opens the URL in a browser, no charge occurs during creation, and predictable errors occur when the listing is missing, the add-on is free early access, or payments are not configured. This gives the agent an accurate model of side effects without contradicting the annotations.

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?

The description is compact and front-loaded: the first sentence states the outcome, the second sets the buyer-authorization expectation, and the third lists failure cases. Every sentence adds distinct value with no 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?

Given the required parameters, an output schema, and the relevant annotations, the description is complete enough for an agent to call the tool correctly. It explains the main caveat of creating a checkout link, when it errors, and that the resulting URL is for a human to complete, leaving no critical runtime surprise unexplained.

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?

The description does not elaborate on the parameters themselves, but the input schema fully documents both slug and product, including the product enum and pointer to list_offers. Since schema description coverage is 100%, the description adds no additional parameter semantics; the schema carries that weight.

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 a specific action and resource: creating a Stripe checkout URL for one paid add-on on one listing. It also clarifies the intended recipient is a human, which distinguishes this tool from purchase-completion or listing-management siblings.

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?

The description clearly conveys when the tool is appropriate: whenever a checkout link for a paid add-on is needed before a human completes payment. It also gives important negative context by stating that this is not a completed purchase and will error in non-purchasable cases. It does not explicitly route the agent to sibling tools or name alternatives, though the schema pointing to list_offers partially fills that gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Launchelion tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?