Skip to main content
Glama

Create Checkout Link

create_checkout_link

Generates a shareable checkout link for a domain listing. Only share with intended buyers to initiate purchase.

Instructions

Generate a shareable checkout/purchase link for a SellerHub domain listing. WARNING: Anyone with this link can initiate a purchase of the domain. Only share with intended buyers. Always confirm with the user before generating a checkout link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesCheckout link type. Currently "buyNow" is the supported type.
domainYesThe domain name to create a checkout link for.
basePriceNoOptional base price override for the checkout link (e.g. { amount: "9999", currency: "USD" }).
Behavior4/5

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

The description discloses a critical behavioral trait: 'Anyone with this link can initiate a purchase of the domain.' This adds significant context beyond the annotations (which only indicate non-read-only, non-destructive, etc.). No contradictions with 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 concise and front-loaded, consisting of two sentences plus a brief warning. Every sentence adds value, with no wasted words.

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?

While the description lacks return value details (no output schema), the three parameters are well-documented in the schema. The warning provides essential safety context. Minor gap in not describing the output, but overall sufficient.

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%, so the schema already documents all parameters. The description does not add new parameter details beyond the schema, but it reinforces the purpose. Baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Generate a shareable checkout/purchase link for a SellerHub domain listing.' This is a specific verb-resource combination that distinguishes it from sibling tools, none of which generate checkout links.

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 includes a clear warning about the link's purchasing power and advises to 'Always confirm with the user before generating a checkout link.' This provides when-to-use and when-not-to-use guidance, though it does not explicitly mention alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BartWaardenburg/spaceship-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server