Cloud MCPcampaign
campaign
9 MCP tools on the Hanzo cloud door that call the campaign API.
The 9 tools tools/list names for campaign. Each dispatches to an operation in the campaign API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_campaign_id | DELETE /v1/campaign/{id} | 1 | DeleteCampaign removes one campaign of the caller's org and answers 204 with no body. |
delete_v1_campaign_id_channels_kind | DELETE /v1/campaign/{id}/channels/{kind} | 2 | RemoveCampaignChannel drops one channel from a campaign and returns the updated campaign. |
get_v1_campaign | GET /v1/campaign | 2 | ListCampaigns returns the org's campaigns, newest first, optionally narrowed to one status. |
get_v1_campaign_id | GET /v1/campaign/{id} | 1 | GetCampaign returns one campaign of the caller's org — its name, audience, creatives, channels with |
get_v1_campaign_id_metrics | GET /v1/campaign/{id}/metrics | 4 | CampaignMetrics returns a campaign's results over a window: the analytics funnel (impressions, click |
get_v1_campaign_summary | GET /v1/campaign/summary | 0 | SummarizeCampaigns returns the org's go-to-market roll-up: how many campaigns exist, how many are li |
post_v1_campaign | POST /v1/campaign | 6 | CreateCampaign creates a campaign as a DRAFT and returns it. |
post_v1_campaign_id_channels | POST /v1/campaign/{id}/channels | 4 | AddCampaignChannel adds a channel to a campaign, or REPLACES the one it already has of that kind, an |
put_v1_campaign_id | PUT /v1/campaign/{id} | 7 | UpdateCampaign rewrites a campaign's core fields — name, audience, creatives, schedule and budget — |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?