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. Once it is launched its channels carry provider state (an external id, a live status), so they are added and removed explicitly through the channels sub-resource instead; a whole-object write would silently orphan a running execution.

Arguments

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.

Object types

ChannelSpec is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

ChannelSpec

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": "put_v1_campaign_id",
         "arguments": {
           "audience": "<audience>",
           "budget": 0,
           "channels": [
             {
               "account": "<account>",
               "detail": "<detail>",
               "externalId": "<externalId>",
               "kind": "<kind>",
               "platform": "<platform>",
               "status": "<status>"
             }
           ],
           "content": [
             "<content>"
           ],
           "id": "<id>",
           "name": "<name>",
           "scheduleAt": 0
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. budget and scheduleAt 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

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).