Skip to main content
Glama

lemonsqueezy

by io.usefulapi

Update subscription

lemonsqueezy_update_subscription
Destructive

WRITE: Modify a LIVE subscription — change plan/tier (variant_id), cancel, pause/unpause, or set the billing anchor. This affects a real customer's billing. API: PATCH /subscriptions/{id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pauseNoPause object (mode, resumes_at), or null to unpause.
cancelledNoSet true to cancel, false to un-cancel.
variant_idNoNew variant id to switch the plan/tier to.
billing_anchorNoDay of month (1-31) to anchor billing to.
subscription_idYesSubscription id to update (required).

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already set destructiveHint=true. The description adds context that it affects 'a real customer's billing' and lists concrete modifications, which is helpful beyond the annotation.

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 with no wasted words. Front-loaded with 'WRITE:' to signal action type, then lists possible modifications clearly.

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?

Mutation tool with no output schema; description does not mention return values. While it provides intent, it could be more complete by hinting at the response structure or error conditions.

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 covers all parameters with descriptions (100% coverage). The description adds a high-level summary but no additional meaning beyond what the schema provides.

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 action (Modify), resource (LIVE subscription), and specific changes (plan/tier, cancel, pause/unpause, billing anchor). It distinguishes from sibling tools like cancel_subscription by covering a broader set of modifications.

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 guidance on when to use this tool versus alternatives like cancel_subscription. The description does not specify prerequisites, exclusions, or preferred scenarios.

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