post_v1_marketing_calendar

Adds a post to the content calendar. Channel and body are required. A scheduledAt in the future makes the post "scheduled" and the durable sweep publishes it when it comes due — claimed once, so a post publishes at most once; without one it stays a draft.


Tool	`post_v1_marketing_calendar`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	10
Operation	`POST /v1/marketing/calendar`
Product	marketing

Arguments

Field	Type	Required	Default	Values	Description
`body`	`string`	—	—	—	Body is the post text. Required.
`channel`	`string`	—	—	—	Channel is the target network: x, facebook, instagram, linkedin, tiktok, youtube or threads. Required — a post must name where it goes.
`createdAt`	`integer`	—	—	—	CreatedAt and UpdatedAt are unix seconds, both server-assigned.
`error`	`string`	—	—	—	Error is the exact reason the last publish attempt failed — the honest record behind a "failed" status, never a faked success.
`id`	`string`	—	—	—	ID is the server-assigned post id ("cal_" + 128 random bits).
`publishedAt`	`integer`	—	—	—	PublishedAt is when the publish succeeded; 0 until it does.
`scheduledAt`	`integer`	—	—	—	ScheduledAt is the unix publish time; 0 leaves the post a draft, and any value makes it "scheduled" for the durable sweep to pick up.
`status`	`string`	—	—	—	Status is draft, scheduled, published, failed or canceled. Server-owned.
`title`	`string`	—	—	—	Title is the post's internal label, capped at 1024 bytes.
`updatedAt`	`integer`	—	—	—	—

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_marketing_calendar",
         "arguments": {
           "body": "<body>",
           "channel": "<channel>",
           "createdAt": 0,
           "error": "<error>",
           "id": "<id>",
           "publishedAt": 0,
           "scheduledAt": 0,
           "status": "<status>",
           "title": "<title>",
           "updatedAt": 0
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. createdAt, publishedAt, scheduledAt and updatedAt 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_marketing_calendar`	`POST /v1/marketing/calendar`	marketing	Adds a post to the content calendar.

The same capability over plain HTTP is in the marketing 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).

post_v1_marketing_calendar

Arguments

Call it

The operation behind it

On this page