post_v1_marketing_campaigns
Registers a campaign in the caller's org. Name is required; channel defaults to email and status to draft, and a future scheduledAt with no explicit status makes the campaign "scheduled".
Registers a campaign in the caller's org. Name is required; channel defaults to email and status to draft, and a future scheduledAt with no explicit status makes the campaign "scheduled". Budget and spend are cents and are clamped to >= 0. The id, createdAt and updatedAt of the input are ignored — the server assigns them.
| Tool | post_v1_marketing_campaigns |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 10 |
| Operation | POST /v1/marketing/campaigns |
| Product | marketing |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
budget | integer | — | — | — | Budget and Spend are minor units (USD cents), clamped to >= 0. |
channel | string | — | — | — | Channel is the delivery surface: email, sms, social, meta, google or tiktok. Empty means email. |
createdAt | integer | — | — | — | CreatedAt and UpdatedAt are unix seconds, both server-assigned. |
id | string | — | — | — | ID is the server-assigned campaign id ("camp_" + 128 random bits). |
name | string | — | — | — | Name is the campaign's label. Required, trimmed, capped at 1024 bytes. |
objective | string | — | — | — | Objective is the free-text goal ("signups"), capped at 1024 bytes. |
scheduledAt | integer | — | — | — | ScheduledAt is the unix send time; 0 means unscheduled. Setting it on a campaign with no explicit status makes that status "scheduled". |
spend | integer | — | — | — | — |
status | string | — | — | — | Status is the lifecycle: draft, scheduled, active, paused or completed. Empty means draft. |
updatedAt | integer | — | — | — | — |
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_campaigns",
"arguments": {
"budget": 0,
"channel": "<channel>",
"createdAt": 0,
"id": "<id>",
"name": "<name>",
"objective": "<objective>",
"scheduledAt": 0,
"spend": 0,
"status": "<status>",
"updatedAt": 0
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. budget, createdAt, scheduledAt, spend and updatedAt hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are 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_campaigns | POST /v1/marketing/campaigns | marketing | Registers a campaign in the caller's org. |
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?