Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs

ls_create_discount

Create discount codes for your Lemon Squeezy store. Supports percentage or fixed discounts, with duration, usage limits, and optional product restrictions.

Instructions

Create a new discount code. Supports percentage or fixed amount discounts with optional duration and usage limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storeIdYesThe store ID to create the discount in
nameYesInternal name for the discount
codeYesThe discount code customers will enter (e.g. 'SAVE20')
amountYesDiscount amount — in cents for 'fixed' type (e.g. 1000 = $10.00), or percentage for 'percent' type (e.g. 20 = 20%)
amountTypeYesDiscount type: 'percent' or 'fixed'
durationNoHow long the discount applies: 'once' (first payment only), 'repeating' (for N months), or 'forever' (default)
durationInMonthsNoNumber of months the discount applies (required when duration is 'repeating')
maxRedemptionsNoMaximum number of times this discount can be redeemed (0 = unlimited)
startsAtNoWhen the discount becomes active (ISO 8601 format)
expiresAtNoWhen the discount expires (ISO 8601 format)
isLimitedToProductsNoIf true, the discount only applies to specific variants (set via variantIds)
variantIdsNoArray of variant IDs this discount applies to (requires isLimitedToProducts: true)
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond that. It does not disclose side effects, permission requirements, or whether the operation is idempotent (idempotentHint=false).

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?

Two sentences, front-loaded with the core action 'Create a new discount code'. Every sentence adds value without redundancy or fluff.

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?

No output schema, but the description gives a broad overview. For a tool with 12 parameters (5 required), it lacks details on parameter interdependencies (e.g., durationInMonths required when duration='repeating'), though these are present in the schema. Adequate but not comprehensive.

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 all parameters have descriptions. The description reinforces the purpose of amountType (percentage/fixed) and optional duration/usage limits, but does not add significant new meaning beyond what the schema already provides. Baseline 3.

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 it creates a new discount code, and specifies support for percentage or fixed amount discounts with optional duration and usage limits. This distinguishes it from sibling tools like ls_get_discount (read) and ls_delete_discount (delete).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives, such as when to use ls_create_checkout or other creation tools. The description implies it's for creating discounts, but does not mention prerequisites or exclusions.

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/YawLabs/lemonsqueezy-mcp'

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