get_v1_ads_campaigns_id
Returns one of the caller org's campaigns.
Returns one of the caller org's campaigns. An id another org owns reads as not found, so the response cannot confirm that it exists.
| Tool | get_v1_ads_campaigns_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | GET /v1/ads/campaigns/{id} |
| Product | ads |
Arguments
The door declares no arguments for this tool.
GET /v1/ads/campaigns/{id} requires id, which tools/list does not declare on this tool. Where that value goes in a tools/call is not something the door publishes, so this page does not guess — the same capability over plain HTTP is fully specified in the API reference below.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty — though the operation behind it requires id, so this envelope is the shape of the call, not one that can name a resource.
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_ads_campaigns_id",
"arguments": {}
}
}'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 |
|---|---|---|---|
get_v1_ads_campaigns_id | GET /v1/ads/campaigns/{id} | ads | Returns one of the caller org's campaigns. |
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?
get_v1_ads_campaigns
Returns the caller org's ad campaigns, most recently updated first, optionally narrowed to one lifecycle status.
get_v1_ads_summary
Rolls the caller org's ad campaigns up into four numbers: how many campaigns exist, how many are active, and the summed budget and spend across all of them.