Skip to main content
Glama
Sign In
@yawlabs/lemonsqueezy-mcp

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ls_create_checkout

Generate a checkout URL for a product variant so customers can complete a purchase. Customize pricing, prefill customer data, and apply discounts to streamline the checkout process.

Instructions

Create a new checkout URL for a product variant. Returns a URL where the customer can complete their purchase. Supports custom pricing, prefilled customer data, and checkout customization.

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": {
      "storeId": "<storeId>",
      "variantId": "<variantId>"
    },
    "name": "ls_create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPrefill customer name
emailNoPrefill customer email
storeIdYesThe store ID
expiresAtNoCheckout expiry date (ISO 8601 format)
taxNumberNoPrefill tax/VAT number
variantIdYesThe variant ID for the product being purchased
customDataNoCustom data object to attach to the order
customPriceNoCustom price in cents (overrides the variant price)
discountCodeNoPre-apply a discount code
enabledVariantsNoArray of variant IDs to show on the checkout (for products with multiple variants)
billingAddressZipNoPrefill billing ZIP/postal code
billingAddressCountryNoPrefill billing country (ISO 3166-1 alpha-2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.2
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv0.10.10

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish this is a mutation (readOnlyHint=false) and not idempotent. The description adds that it returns a URL and that it supports custom pricing, prefill, and customization, but it does not disclose side effects, auth requirements, or behavior around expiry/payment. This is acceptable but not rich.

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 short sentences with the core action front-loaded. There is minor redundancy ('Create a new checkout URL' vs 'Returns a URL...') but no filler or irrelevant detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, a required storeId/variantId pair, and no output schema, the description gives a useful high-level summary but omits the exact response shape and any edge-case behavior. The schema covers parameter details, but the tool's output contract is only described as 'a URL'.

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 every parameter is individually documented. The description's mention of 'custom pricing, prefilled customer data, and checkout customization' only groups existing schema capabilities without adding new meaning beyond the schema. Baseline 3 applies.

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 opens with a specific verb and resource: 'Create a new checkout URL for a product variant,' and immediately clarifies the output (the purchase URL). This clearly distinguishes the tool from sibling read tools like ls_get_checkout and ls_list_checkouts.

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 use case is clear: you use this when you need to generate a checkout URL for a variant. However, the description never explicitly names alternatives or states when not to use the tool; the distinction from siblings is implied by the create verb rather than stated.

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

Deploy Server

Other Tools