post_v1_ads_campaigns
Registers a new ad campaign for the caller's org and answers 201 with the stored row.
Registers a new ad campaign for the caller's org and answers 201 with the stored row. It only records the campaign — nothing is sent to the ad network until POST /v1/ads/campaigns/{id}/launch runs it. The org is stamped by the server from the validated principal, so a body can never place a campaign in another tenant.
| Tool | post_v1_ads_campaigns |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 7 |
| Operation | POST /v1/ads/campaigns |
| Product | ads |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
account | string | — | — | — | Account is the provider ad-account this campaign runs on (Meta act_<id>). Optional. |
budget | integer | — | — | — | Budget is the campaign budget in MINOR units (cents). Negative values clamp to 0. |
name | string | — | — | — | Name is the campaign's display label. Required; trimmed and bounded to 1024 bytes. |
objective | string | — | — | — | Objective is the campaign goal as the provider names it. Optional, bounded to 1024 bytes. |
platform | string | — | — | — | Platform is the ad network: meta, google, tiktok or x. Empty defaults to meta. |
spend | integer | — | — | — | Spend is the amount spent so far in MINOR units (cents). Negative values clamp to 0. |
status | string | — | — | — | Status is the lifecycle state: draft, active, paused or completed. Empty defaults to draft. |
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_ads_campaigns",
"arguments": {
"account": "<account>",
"budget": 0,
"name": "<name>",
"objective": "<objective>",
"platform": "<platform>",
"spend": 0,
"status": "<status>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. budget and spend 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_ads_campaigns | POST /v1/ads/campaigns | ads | Registers a new ad campaign for the caller's org and answers 201 with the stored row. |
The same capability over plain HTTP is in the ads 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?