Kit MCP Server

Overview Schema Source Related Servers Discussions Admin

Update a sequence

update_sequence

Destructive

Modify an email sequence's settings, schedule, or active status. Requires confirm=true because changes may affect delivery or subscriber state.

Instructions

Update a sequence. May affect delivery, audience membership, published data or irreversible state. Requires confirm=true.

Input Schema

TableJSON Schema

Name	Required	Description
`hold`	No	When `true`, subscribers added via Visual Automations stay in the sequence after receiving the last email.
`name`	No	The name of the sequence.
`active`	No	`true` to activate the sequence, `false` to deactivate it.
`repeat`	No	When `true`, subscribers can restart the sequence multiple times.
`account`	No	Named private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
`send_days`	No	The days of the week to send the sequence on. Must be one of: `monday`, `tuesday`, `wednesday`, `thursday`, `friday`, `saturday`, `sunday`.
`send_hour`	No	The hour of the day to send the sequence at. Must be an integer between 0 and 23.
`time_zone`	No	The timezone to use for the sequence. Must be a valid IANA timezone string.
`sequence_id`	Yes	Positive sequence id.
`payload_file`	No	Local JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
`email_address`	No	The sending email address to use. Uses the account's sending email address if not provided.
`email_template_id`	No	Id of the email template to use.
`exclude_subscriber_sources`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.0Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "exclude_subscriber_sources": {
+    "description": "The subscriber sources to exclude from the sequence.",
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "ids": {
+          "items": {
+            "description": "The ids of the subscriber sources to exclude.",
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        "type": {
+          "description": "The type of subscriber source to exclude. Must be one of: `tag`, `sequence`, `form`, `segment`.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "ids"
+      ],
+      "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 / exclude_subscriber_sources / $ref
```
Added value: +"#/$defs/exclude_subscriber_sources"
```
removedInput schema / properties / exclude_subscriber_sources / description
```
Removed value: -"The subscriber sources to exclude from the sequence."
```

removedInput schema / properties / exclude_subscriber_sources / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "ids": {
-      "items": {
-        "description": "The ids of the subscriber sources to exclude.",
-        "type": "integer"
-      },
-      "type": "array"
-    },
-    "type": {
-      "description": "The type of subscriber source to exclude. Must be one of: `tag`, `sequence`, `form`, `segment`.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "ids"
-  ],
-  "type": "object"
-}

removedInput schema / properties / exclude_subscriber_sources / type
```
Removed value: -"array"
```
addedInput schema / properties / payload / properties / exclude_subscriber_sources / $ref
```
Added value: +"#/$defs/exclude_subscriber_sources"
```
removedInput schema / properties / payload / properties / exclude_subscriber_sources / description
```
Removed value: -"The subscriber sources to exclude from the sequence."
```

removedInput schema / properties / payload / properties / exclude_subscriber_sources / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "ids": {
-      "items": {
-        "description": "The ids of the subscriber sources to exclude.",
-        "type": "integer"
-      },
-      "type": "array"
-    },
-    "type": {
-      "description": "The type of subscriber source to exclude. Must be one of: `tag`, `sequence`, `form`, `segment`.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "ids"
-  ],
-  "type": "object"
-}

removedInput schema / properties / payload / properties / exclude_subscriber_sources / type
```
Removed value: -"array"
```

First observedv2.0.1Oct 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety bar is lower. The description still adds real value by naming what may be affected ("delivery, audience membership, published data or irreversible state") and surfacing the confirm=true requirement, going beyond the raw hints.

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?

Two sentences, both front-loaded: the action first, then the risk scope, then the confirm requirement. No filler, and the most important constraint (irreversibility + confirm) is not buried.

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 15-parameter, nested-object, destructive mutation with no output schema, the description is thin: it never clarifies how payload, payload_file, and individual body flags relate, nor the account selector. The schema carries that load, but the description is only minimally complete for the tool's complexity.

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 93%, so the schema already documents all 15 parameters thoroughly (payload vs flags, payload_file, account, send_days, etc.). The description adds no parameter-level detail beyond restating the confirm requirement, 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 clear verb+resource ("Update a sequence"), so an agent knows it mutates an existing sequence. However it does not differentiate from close siblings like update_sequence_email, update_broadcast, or create_sequence, leaving the agent to infer scope from the name alone.

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?

It states the precondition "Requires confirm=true," which is a useful invocation rule, but gives no when-to-use/when-not guidance and never names an alternative (e.g. update_sequence_email) that would help the agent pick the right sibling. Context for choosing this tool is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Update a sequence

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools