post_v1_campaign_id_channels
AddCampaignChannel adds a channel to a campaign, or REPLACES the one it already has of that kind, and returns the updated campaign.
AddCampaignChannel adds a channel to a campaign, or REPLACES the one it already has of that kind, and returns the updated campaign.
A campaign carries at most one channel per kind, because the kind IS the executor: adding a second "paid" channel would mean two ad accounts running one campaign with no way to tell their results apart. The new channel starts "pending" — adding it does not launch it.
| Tool | post_v1_campaign_id_channels |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/campaign/{id}/channels |
| Product | campaign |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
account | string | — | — | — | Account is the provider account this channel runs under: an ad-account, a page, or a mailing-list id. |
id | string | — | — | — | ID is the campaign to add the channel to, from the path. |
kind | string | — | — | — | Kind is the channel kind and the identity a campaign holds at most one of: paid, organic or email. |
platform | string | — | — | — | Platform is the provider within the kind — meta, google, x, instagram, or the email provider. |
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_campaign_id_channels",
"arguments": {
"account": "<account>",
"id": "<id>",
"kind": "<kind>",
"platform": "<platform>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source 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_campaign_id_channels | POST /v1/campaign/{id}/channels | campaign | Adds a channel to a campaign, or REPLACES the one it already has of that kind, and… |
The same capability over plain HTTP is in the campaign 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?
post_v1_campaign
CreateCampaign creates a campaign as a DRAFT and returns it. A draft is inert: nothing is sent, no connector is touched and no budget is committed until the campaign is launched.
put_v1_campaign_id
UpdateCampaign rewrites a campaign's core fields — name, audience, creatives, schedule and budget — and returns the updated campaign. Channels are replaced ONLY while the campaign is still a draft.