Skip to main content
Glama

lemonsqueezy

by io.usefulapi

List variants

lemonsqueezy_list_variants
Read-only

List variants (price/plan tiers), optionally filtered to one product. API: GET /variants (filter[product_id]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoComma-separated related resources to sideload (JSON:API include=), e.g. 'store,variant'.
page_sizeNoResults per page (JSON:API page[size], max 100). Default 10.
product_idNoFilter to a single product id.
page_numberNoPage number (JSON:API page[number]). Default 1.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds the API endpoint and filter parameter but doesn't elaborate on pagination or result format.

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?

Single sentence efficiently conveys purpose and key filter option. No redundant information.

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?

Adequate for a simple list tool with good annotations; lacks description of return format but includes API reference.

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 provides full descriptions for all parameters. The description adds minimal value beyond the schema by referencing the filter[product_id] syntax.

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?

Clearly states the tool lists variants (price/plan tiers) and mentions optional filtering by product. Distinguishes from sibling list tools targeting other resources.

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

Usage Guidelines3/5

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

Implies usage with optional product_id filter, but no explicit guidance on when to use this tool versus alternatives like list_prices or list_products.

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

All lemonsqueezy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (get vs list for each entity, plus specific write operations). Filtering parameters further distinguish list tools. No overlapping purposes.

Naming Consistency5/5

All tools follow a consistent `lemonsqueezy_action_resource` pattern using lowercase and underscores. Actions are consistently get, list, create, cancel, or update.

Tool Count5/5

18 tools cover a broad set of resources (customers, orders, stores, subscriptions, discounts, license keys, prices, products, invoices, variants, checkouts) for a comprehensive e-commerce platform. Each tool earns its place.

Completeness3/5

While reading (list/get) is well-covered for most resources, creation and deletion are missing for many core entities (customers, products, orders, etc.), which may force agents to rely on external processes. Only subscriptions and checkouts have write support.

Resources