Skip to main content
Glama
thenavidm

Lemon Squeezy MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update subscription

update_subscription
Destructive

Modify a subscription by ID to pause, cancel, change variant, set trial end, billing anchor, prorations, or invoice immediately.

Instructions

Updates the subscription with the given ID and provided attributes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExact opaque native resource ID; no traversal or URL.
pauseNo
accountNoExact private profile label. Does not prove store ownership; mode applies to the main API key only.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete native JSON object body. JSON:API uses data/type/id/attributes/relationships. No mixing with body flags or payload_file. License credential is private configuration, never body input.
cancelledNo
variant_idNo
payload_fileNoAbsolute regular non-symlink native JSON body file at most 1 MiB; cannot mix with payload or body flags.
trial_ends_atNo
billing_anchorNo
disable_prorationsNo
invoice_immediatelyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "pause": {
+    "anyOf": [
+      {
+        "type": "null"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "mode": {
+            "enum": [
+              "void",
+              "free"
+            ],
+            "type": "string"
+          },
+          "resumes_at": {
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "mode"
+        ],
+        "type": "object"
+      }
+    ]
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Explicit approval for this requested effect, including private output files."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / pause / $ref
      Added value: +"#/$defs/pause"
    • removedInput schema / properties / pause / anyOf
      Removed value: -[
-  {
-    "type": "null"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "mode": {
-        "enum": [
-          "void",
-          "free"
-        ],
-        "type": "string"
-      },
-      "resumes_at": {
-        "format": "date-time",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "mode"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties / payload / properties / data / properties / attributes / properties / pause / $ref
      Added value: +"#/$defs/pause"
    • removedInput schema / properties / payload / properties / data / properties / attributes / properties / pause / anyOf
      Removed value: -[
-  {
-    "type": "null"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "mode": {
-        "enum": [
-          "void",
-          "free"
-        ],
-        "type": "string"
-      },
-      "resumes_at": {
-        "format": "date-time",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "mode"
-    ],
-    "type": "object"
-  }
-]
  2. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true, idempotentHint=false, and openWorldHint=true, lowering the bar. But the description adds nothing beyond that: it does not say what gets mutated, whether changes are reversible, or how the payload/body-flag duality behaves. No contradiction, but no added behavioral context either.

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?

A single front-loaded sentence with no filler. It is appropriately tight, though the brevity reflects under-specification rather than deliberate economy.

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

Completeness2/5

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

This is a complex mutation with 12 parameters, nested objects, and a payload-vs-body-flags mutual exclusion, yet the description explains none of it. Annotations carry the safety profile and the schema documents many fields, but the description leaves the agent without the overview needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 42% across 12 parameters, so the description must compensate and does not. 'Given ID and provided attributes' restates what the schema already names without clarifying any of the undocumented parameters (pause, confirm, payload vs payload_file, disable_prorations, invoice_immediately, billing_anchor).

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?

The description states a clear verb (Updates) and resource (the subscription) and adds the targeting detail (with the given ID and provided attributes). However, it offers no differentiation from closely related siblings like cancel_subscription or update_subscription_item, which an agent must distinguish between.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is not told when to prefer this over cancel_subscription, update_subscription_item, or get_subscription, even though all appear as siblings.

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