Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bulk tag subscribers

bulk_tag_subscribers
Destructive

Apply tags to multiple subscribers in one request to organize audiences or trigger automations. Requires OAuth and confirm=true because it can change audience membership.

Instructions

Bulk tag 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.
taggingsNo
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: +{
+  "taggings": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "subscriber_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "tag_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "tag_id",
+        "subscriber_id"
+      ],
+      "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 / taggings / $ref
      Added value: +"#/$defs/taggings"
    • removedInput schema / properties / payload / properties / taggings / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "subscriber_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "tag_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "tag_id",
-    "subscriber_id"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / payload / properties / taggings / type
      Removed value: -"array"
    • addedInput schema / properties / taggings / $ref
      Added value: +"#/$defs/taggings"
    • removedInput schema / properties / taggings / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "subscriber_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "tag_id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "tag_id",
-    "subscriber_id"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / taggings / type
      Removed value: -"array"
  2. First observedv2.0.1

TDQS

B3.1/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false, openWorldHint=true), the description adds two genuinely useful behavioral facts: the mandatory confirm=true gate and the authentication constraint that API keys do not work here. The impact clause is boilerplate, but the auth and confirmation details are real added value.

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, front-loaded sentences with no padding. The impact sentence is generic filler, but the ordering (action, impact, confirm gate, auth) is efficient.

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, non-idempotent bulk mutation with a nested taggings array and no output schema, the description covers safety, confirmation, and auth but omits key semantics such as whether tagging appends or replaces existing taggings and what the bulk result looks like. Adequate but with clear gaps.

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% and the description only restates the confirm requirement, which the schema already documents ('Set true only when the user asked for exactly this action'). It adds no meaning for the taggings structure, payload/payload_file alternatives, or callback_url, so it neither compensates for nor extends the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence 'Bulk tag subscribers' essentially restates the tool name and title, adding only the notion of bulk. The action is understandable, but nothing distinguishes it from siblings like tag_subscriber, untag_subscriber, or bulk_remove_tags_from_subscribers.

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 when-to-use guidance is given relative to alternatives. 'Requires confirm=true' and the OAuth requirement are prerequisites rather than routing guidance, and the agent is left to infer when bulk tagging is preferable to single-subscriber tag_subscriber calls.

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