post_v1_marketing_sequences_id_steps
Appends a message to the END of a sequence: the new step's idx is one past the last, so steps arrive in the order they are added. Body is required and delaySeconds must be >= 0.
Appends a message to the END of a sequence: the new step's idx is one past the last, so steps arrive in the order they are added. Body is required and delaySeconds must be >= 0. Adding a step does not disturb enrollments already walking — one that has passed this index simply never sees it.
| Tool | post_v1_marketing_sequences_id_steps |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/marketing/sequences/{id}/steps |
| Product | marketing |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
body | string | — | — | — | Body is the message text. Required. |
delaySeconds | integer | — | — | — | DelaySeconds is how long after the previous step this one sends (after enrollment, for the first step). Must be >= 0. |
id | string | — | — | — | SequenceID is the sequence id from the path (the route's :id). |
subject | string | — | — | — | Subject is the email subject line, capped at 1024 bytes. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_marketing_sequences_id_steps",
"arguments": {
"body": "<body>",
"delaySeconds": 0,
"id": "<id>",
"subject": "<subject>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. delaySeconds holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_marketing_sequences_id_steps | POST /v1/marketing/sequences/{id}/steps | marketing | Appends a message to the END of a sequence: the new step's idx is one past the last, so… |
The same capability over plain HTTP is in the marketing API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?