Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bulk add subscribers to forms

bulk_add_subscribers_to_forms
Destructive

Add multiple subscribers to Kit forms at once, with OAuth and confirm=true required to prevent unintended audience or delivery changes.

Instructions

Bulk add subscribers to forms. 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.
additionsNo
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: +{
+  "additions": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "form_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "referrer": {
+          "type": "string"
+        },
+        "subscriber_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "form_id",
+        "subscriber_id"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / additions / $ref
      Added value: +"#/$defs/additions"
    • removedInput schema / properties / additions / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "form_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "referrer": {
-      "type": "string"
-    },
-    "subscriber_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "form_id",
-    "subscriber_id"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / additions / type
      Removed value: -"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 / additions / $ref
      Added value: +"#/$defs/additions"
    • removedInput schema / properties / payload / properties / additions / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "form_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "referrer": {
-      "type": "string"
-    },
-    "subscriber_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "form_id",
-    "subscriber_id"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / payload / properties / additions / type
      Removed value: -"array"
  2. First observedv2.0.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, the description specifies what can be affected: 'delivery, audience membership, published data or irreversible state.' It also adds concrete operational requirements: confirm=true and OAuth-only authentication. This is rich behavioral context that annotations alone do not provide.

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?

The description is four sentences, front-loaded with the action, then immediately states impact, confirmation, and auth constraints. Every sentence carries safety or prerequisite information without padding.

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 complex bulk mutation with nested objects and no output schema, the description covers purpose, risk profile, confirmation, and authentication. It leaves detailed payload structure to the schema, which is acceptable, but it could say more about the return or async behavior if applicable.

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 description coverage is 67%, so the schema already documents several parameters. The description adds one important parameter-level constraint by declaring confirm=true required, but it does not explain the nested additions structure, payload vs payload_file, or callback_url. A baseline of 3 is appropriate.

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 states a specific verb and resource: 'Bulk add subscribers to forms.' The bulk scope is clear and distinguishes it from the singular add_subscriber_to_form siblings, even without naming them.

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

Usage Guidelines4/5

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

It gives clear prerequisites ('Requires confirm=true') and auth constraints ('Requires OAuth; API keys are not supported'), which frame when the tool can be used. It does not explicitly route agents away from the singular alternatives, so it stops short of full when/when-not guidance.

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