Hanzo
Cloud MCPcampaign

get_v1_campaign_id

GetCampaign returns one campaign of the caller's org — its name, audience, creatives, channels with their per-channel launch state, schedule, budget and status.

GetCampaign returns one campaign of the caller's org — its name, audience, creatives, channels with their per-channel launch state, schedule, budget and status. 404 when the org has no campaign with that id.

Toolget_v1_campaign_id
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments1, 1 required
OperationGET /v1/campaign/{id}
Productcampaign

Arguments

FieldTypeRequiredDefaultValuesDescription
idstringyesID is the campaign's server-minted handle, "cmp_"-prefixed.

tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/campaign/{id}, the operation this tool dispatches to — the same declaration the REST API validates against. 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. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

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": "get_v1_campaign_id",
         "arguments": {
           "id": "<id>"
         }
       }
     }'

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

OperationRouteProductSummary
get_v1_campaign_idGET /v1/campaign/{id}campaignReturns one campaign of the caller's org — its name, audience, creatives, channels with…

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?

On this page