Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bulk create subscribers

bulk_create_subscribers
Destructive

Add many subscribers to a Kit account in one call, with optional names, email addresses, and states. Requires confirm=true and OAuth to prevent unintended audience changes.

Instructions

Bulk create subscribers. 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.
subscribersNo
callback_urlNo
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. Changed8 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "subscribers": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "email_address": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "first_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "state": {
+          "enum": [
+            "active",
+            "cancelled",
+            "bounced",
+            "complained",
+            "inactive"
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • 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 / subscribers / $ref
      Added value: +"#/$defs/subscribers"
    • removedInput schema / properties / payload / properties / subscribers / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "email_address": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "first_name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "state": {
-      "enum": [
-        "active",
-        "cancelled",
-        "bounced",
-        "complained",
-        "inactive"
-      ],
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / payload / properties / subscribers / type
      Removed value: -"array"
    • addedInput schema / properties / subscribers / $ref
      Added value: +"#/$defs/subscribers"
    • removedInput schema / properties / subscribers / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "email_address": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "first_name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "state": {
-      "enum": [
-        "active",
-        "cancelled",
-        "bounced",
-        "complained",
-        "inactive"
-      ],
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / subscribers / type
      Removed value: -"array"
  2. First observedv2.0.1

TDQS

A3.6/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 bar is lower; the description nonetheless adds the confirm=true guardrail and the OAuth-vs-API-key constraint, plus a warning about side effects on delivery/audience/published data. The side-effect sentence is somewhat generic boilerplate, which keeps it from a 5.

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?

Three short sentences, front-loaded with the purpose, then the risk warning, then the hard requirements. Efficient overall, though the vague 'May affect delivery, audience membership, published data or irreversible state' phrasing spends words without pinning down a concrete consequence.

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?

For a destructive bulk mutation with no output schema this covers the essentials (auth, confirmation, side effects), but omits practical operational details an agent would want: whether the call is async given the callback_url parameter, any batch-size limit, and how the three body-input modes relate.

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 67%, so most parameters are documented structurally. The description only reinforces 'confirm' (already described in the schema) and adds nothing about the payload vs. individual body flags vs. payload_file mutual exclusion, nor about the subscribers array shape.

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 opens with a specific verb+resource ('Bulk create subscribers') and the 'Bulk' qualifier implicitly separates it from the single-record create_subscriber sibling. It never names the alternative explicitly, so the agent must infer the distinction, but the core purpose is unambiguous.

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 states two real prerequisites (confirm=true, OAuth-only auth), which is useful gating information, but gives no guidance on when to choose this over create_subscriber, bulk_add_subscribers_to_forms, or other bulk siblings. Usage context is implied by the name rather than explained.

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