Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a purchase

create_purchase
Destructive

Record a purchase for a subscriber in Kit to track transactions, update audience membership, and trigger delivery actions. Requires OAuth and confirm=true.

Instructions

Create a purchase. May affect delivery, audience membership, published data or irreversible state. Requires confirm=true. Requires OAuth; API keys are not supported for this endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoNamed private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
purchaseNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "purchase": {
+    "additionalProperties": false,
+    "properties": {
+      "currency": {
+        "description": "3 letter currency code (e.g. `USD`)",
+        "type": "string"
+      },
+      "discount": {
+        "format": "float",
+        "type": "number"
+      },
+      "email_address": {
+        "description": "The subscriber that the purchase belongs to",
+        "type": "string"
+      },
+      "products": {
+        "description": "Array of purchased products",
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "lid": {
+              "description": "Each product should have a unique `lid` (i.e., line item identifier) for this purchase.",
+              "type": "string"
+            },
+            "name": {
+              "description": "Product name",
+              "type": "string"
+            },
+            "pid": {
+              "description": "This is your identifier for a product. Each product provided in the `products` array must have a unique pid. Variants of the same product should have the same pid.",
+              "type": "string"
+            },
+            "quantity": {
+              "description": "Product quantity",
+              "type": "integer"
+            },
+            "sku": {
+              "description": "Product sku",
+              "type": "string"
+            },
+            "unit_price": {
+              "description": "Product price",
+              "format": "float",
+              "type": "number"
+            }
+          },
+          "required": [
+            "name",
+            "pid",
+            "lid",
+            "quantity",
+            "unit_price",
+            "sku"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "shipping": {
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "subtotal": {
+        "format": "float",
+        "type": "number"
+      },
+      "tax": {
+        "format": "float",
+        "type": "number"
+      },
+      "total": {
+        "format": "float",
+        "type": "number"
+      },
+      "transaction_id": {
+        "type": "string"
+      },
+      "transaction_time": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "email_address",
+      "transaction_id",
+      "status",
+      "subtotal",
+      "tax",
+      "shipping",
+      "discount",
+      "total",
+      "currency",
+      "transaction_time",
+      "products"
+    ],
+    "type": "object"
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for audience/delivery changes, publishing, destructive operations and signing-secret changes. Use only for an action requested by the user."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / payload / properties / purchase / $ref
      Added value: +"#/$defs/purchase"
    • removedInput schema / properties / payload / properties / purchase / additionalProperties
      Removed value: -false
    • removedInput schema / properties / payload / properties / purchase / properties
      Removed value: -{
-  "currency": {
-    "description": "3 letter currency code (e.g. `USD`)",
-    "type": "string"
-  },
-  "discount": {
-    "format": "float",
-    "type": "number"
-  },
-  "email_address": {
-    "description": "The subscriber that the purchase belongs to",
-    "type": "string"
-  },
-  "products": {
-    "description": "Array of purchased products",
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "lid": {
-          "description": "Each product should have a unique `lid` (i.e., line item identifier) for this purchase.",
-          "type": "string"
-        },
-        "name": {
-          "description": "Product name",
-          "type": "string"
-        },
-        "pid": {
-          "description": "This is your identifier for a product. Each product provided in the `products` array must have a unique pid. Variants of the same product should have the same pid.",
-          "type": "string"
-        },
-        "quantity": {
-          "description": "Product quantity",
-          "type": "integer"
-        },
-        "sku": {
-          "description": "Product sku",
-          "type": "string"
-        },
-        "unit_price": {
-          "description": "Product price",
-          "format": "float",
-          "type": "number"
-        }
-      },
-      "required": [
-        "name",
-        "pid",
-        "lid",
-        "quantity",
-        "unit_price",
-        "sku"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "shipping": {
-    "type": "integer"
-  },
-  "status": {
-    "type": "string"
-  },
-  "subtotal": {
-    "format": "float",
-    "type": "number"
-  },
-  "tax": {
-    "format": "float",
-    "type": "number"
-  },
-  "total": {
-    "format": "float",
-    "type": "number"
-  },
-  "transaction_id": {
-    "type": "string"
-  },
-  "transaction_time": {
-    "type": "string"
-  }
-}
    • removedInput schema / properties / payload / properties / purchase / required
      Removed value: -[
-  "email_address",
-  "transaction_id",
-  "status",
-  "subtotal",
-  "tax",
-  "shipping",
-  "discount",
-  "total",
-  "currency",
-  "transaction_time",
-  "products"
-]
    • removedInput schema / properties / payload / properties / purchase / type
      Removed value: -"object"
    • addedInput schema / properties / purchase / $ref
      Added value: +"#/$defs/purchase"
    • removedInput schema / properties / purchase / additionalProperties
      Removed value: -false
    • removedInput schema / properties / purchase / properties
      Removed value: -{
-  "currency": {
-    "description": "3 letter currency code (e.g. `USD`)",
-    "type": "string"
-  },
-  "discount": {
-    "format": "float",
-    "type": "number"
-  },
-  "email_address": {
-    "description": "The subscriber that the purchase belongs to",
-    "type": "string"
-  },
-  "products": {
-    "description": "Array of purchased products",
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "lid": {
-          "description": "Each product should have a unique `lid` (i.e., line item identifier) for this purchase.",
-          "type": "string"
-        },
-        "name": {
-          "description": "Product name",
-          "type": "string"
-        },
-        "pid": {
-          "description": "This is your identifier for a product. Each product provided in the `products` array must have a unique pid. Variants of the same product should have the same pid.",
-          "type": "string"
-        },
-        "quantity": {
-          "description": "Product quantity",
-          "type": "integer"
-        },
-        "sku": {
-          "description": "Product sku",
-          "type": "string"
-        },
-        "unit_price": {
-          "description": "Product price",
-          "format": "float",
-          "type": "number"
-        }
-      },
-      "required": [
-        "name",
-        "pid",
-        "lid",
-        "quantity",
-        "unit_price",
-        "sku"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "shipping": {
-    "type": "integer"
-  },
-  "status": {
-    "type": "string"
-  },
-  "subtotal": {
-    "format": "float",
-    "type": "number"
-  },
-  "tax": {
-    "format": "float",
-    "type": "number"
-  },
-  "total": {
-    "format": "float",
-    "type": "number"
-  },
-  "transaction_id": {
-    "type": "string"
-  },
-  "transaction_time": {
-    "type": "string"
-  }
-}
    • removedInput schema / properties / purchase / required
      Removed value: -[
-  "email_address",
-  "transaction_id",
-  "status",
-  "subtotal",
-  "tax",
-  "shipping",
-  "discount",
-  "total",
-  "currency",
-  "transaction_time",
-  "products"
-]
    • removedInput schema / properties / purchase / type
      Removed value: -"object"
  2. First observedv2.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new operational context beyond that: concrete downstream effects (delivery, audience membership, published data), the confirm gate, and the fact that OAuth is mandatory while API keys are rejected.

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?

Three short sentences, front-loaded with the action and then the risk, confirm gate and auth constraint. No filler and no repetition of the title.

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?

For a 5-parameter, nested-object, no-output-schema mutation tool, the description covers risk, confirmation and authentication, which is what an agent most needs. It omits the mutual exclusivity of the three body-input modes (purchase, payload, payload_file), though that is documented in the schema.

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?

With 80% schema description coverage and a nested purchase object fully documented in the schema, the schema already does the heavy lifting for parameters. The description adds no syntax, format or constraint detail beyond what the schema states, so the baseline 3 applies.

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 specific verb and resource ('Create a purchase') that is clearly distinguishable from the read-side siblings get_purchase and list_purchases. It does not, however, differentiate itself from the many other create_* tools beyond the resource name, which is adequate here since no other tool creates purchases.

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?

It gives one hard prerequisite ('Requires confirm=true') and an auth constraint, which supports correct invocation. It stops short of stating when this tool is preferred over alternatives, what conditions should block a call, or what happens if confirm is omitted.

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