create_playbook
Create a reusable content playbook — an ordered template of content-plan items ("save a repeatable content sequence"). Provide a name and, optionally, the ordered items; each item becomes one content plan when the playbook is instantiated.
Visibility: defaults to "team" (visible to all active teammates). Pass visibility "private" to keep it creator-only.
Anchor date: if the user is building this playbook around a specific real date (a launch, an event, a campaign kickoff), offer to set anchor_date — it's the reference point every item's offset_days counts from, and it becomes the default when they instantiate. It's optional; leave it off for an evergreen/undated template.
The response includes link_url — share it so the user can open the playbook you just created.
When to use: when the user wants to author or save a reusable template/playbook of content plans from scratch (e.g. "make me a launch-week playbook", "save this sequence as a template"). To build a playbook from plans the user already ran, use create_playbook_from_plans instead.
**Links:** present `link_url` to the user exactly as returned — copy it character for character. Never retype, shorten, or rebuild a link or the IDs inside it.Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "create_playbook"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The playbook's title, shown wherever someone browses or picks a playbook to run. Required and trimmed — a blank or whitespace-only value is rejected. It is also the base of the auto-generated cycle name every time the playbook is run ("<name> — Mon YYYY"). | |
| items | No | The ordered steps of the playbook — each entry becomes exactly one content plan when the playbook is run. Every entry needs a `name` (`title` is accepted as an alias) and may also carry description, prompt, blueprint_id, category_id, offset_days and sort_order; array order sets the sequence unless sort_order is given. Optional — omit it to save an empty shell you fill in later, but a playbook with no items cannot be run until you add some. | |
| visibility | No | Optional. Defaults to "team". "private" keeps the playbook creator-only. | |
| anchor_date | No | Optional YYYY-MM-DD anchor date this playbook is built around (e.g. a launch date). Each item's offset_days counts from it, and it becomes the default anchor when instantiating. Offer to set this when the user has a specific date in mind; omit or null for an evergreen/undated template. | |
| description | No | Optional free-text note saying what this playbook is for and when to run it, for teammates browsing the playbook list. It is stored on the playbook only and is never fed into content generation; omit it and it is saved empty. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| name | No | ||
| items | No | ||
| team_id | No | ||
| link_url | No | URL to open this playbook in the Marcora web app — share it so the user can view what you created. | |
| created_at | No | Unix ms timestamp. | |
| created_by | No | ||
| updated_at | No | Unix ms timestamp. | |
| visibility | No | private = creator-only; team = visible to all active teammates. | |
| anchor_date | No | Persisted YYYY-MM-DD anchor date, or null. Each item's offset_days counts from it; it's the default when instantiating. | |
| description | No |