Skip to main content
Glama
mailkite

MailKite

Official

mailkite_create_sequence

Create email sequences with steps, triggers, and input signatures, validating the entire definition at once so you fix all errors in one pass.

Instructions

Create a sequence: a declared input shape, the steps a contact walks over time, and zero or more triggers. A sequence is a function — input is its signature, and every door must satisfy it, so a step's {{input.field}} means the same thing however it was started. Created as a draft unless you pass status "active". The whole definition is validated up front and every problem is reported at once, so you fix a program in one pass rather than one 400 at a time. Requires an API key (mk_live_…).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoDefault sender for every send step, on a verified domain. Required unless every send step carries its own `from`, or trigger.type is "send" (which inherits the triggering message's sender).
nameYesUnique handle for this account; 1-64 chars of letters, digits, dot, dash, or underscore, starting alphanumeric.
inputNoThe sequence's input signature: the shape every door must supply. A sequence is a function and this is how you declare its parameters — steps then read them as {{input.field}}, and a condition can branch on them. Omit it entirely for "anything goes"; you should not need a schema to write a two-step drip.
stepsYesAt least one step, and at least one of them a `send` — a sequence that never sends is a no-op that still costs a row per contact.
exitOnNoSequence-level exits, evaluated before EVERY step. `goal` completes the enrollment — they did the thing, stop chasing, which is the difference between a dunning sequence and harassment. `cancel` abandons it.
statusNoDefaults to `draft`. A sequence enrolls nobody until it is `active`.
reentryNo`once` (default) refuses to enroll a contact already in flight. `always` restarts them: the in-flight enrollment is canceled and a new one begins. `cooldown:<duration>` (e.g. "cooldown:30 days") re-enrolls only when that long has passed since their last enrollment.
triggersNoDoors into this sequence. A bare string is shorthand for { "event": "<name>" }. Replacing the set never bumps the sequence's version and never touches an enrollment in flight. A sequence with no triggers is enrolled only by naming it on a send or calling enroll — which is what "manual" used to mean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations only provide generic false hints, so the description carries the main behavioral load. It explicitly discloses the draft-by-default behavior, the up-front validation of the entire definition, the need for a mk_live_ API key, and the fact that a sequence enrolls nobody until active. This is meaningful and consistent with the annotations; there is no contradiction.

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?

The description is front-loaded with the core purpose and then gives short, useful behavioral details about draft status, validation, and API key requirement. The metaphor of a sequence as a function is compact and adds semantic value without bloating the text.

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?

This is a complex 8-parameter creation tool with no output schema, so the description plus schema still provides enough context to invoke it correctly. The coverage of input semantics, trigger behavior, and default status is strong; task only open concept is the exact output shape, which the description does not describe, but it remains enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all 8 parameters, so the baseline is 3. The description adds genuine extra semantics on top by explaining input as re shared function signature that every trigger must satisfy, and by clarifying what a missing/empty triggers set means. This goes beyond the kind of line-level field descriptions already present in the schema.

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 opening sentence says "Create a sequence" and immediately names the resource's core parts: a declared input shape, the steps a contact walks over time, and triggers. This makes both the verb and the resource unambiguous, and it is easy to tell this tool from list_sequence/get_sequence/update_sequence/delete_sequence peers.

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?

The description gives useful operational context: a sequence starts as a draft unless status active, and a sequence with no triggers can still be used through a send or explicit enroll. However, it does not explicitly say when to choose this tool over alternatives like update_sequence, start_sequence, or stop_sequence, so the tool-selection guidance is implicit rather than direct.

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

Install Server

Other Tools