get_playbook
Fetch one content playbook by id, including its full ordered list of items.
Input Schema
{
"type": "object",
"required": [
"playbook_id"
],
"properties": {
"playbook_id": {
"type": "integer",
"description": "ID of the playbook to fetch."
}
}
}Output Schema
{
"type": "object",
"properties": {
"id": {
"type": "integer"
},
"name": {
"type": "string"
},
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string"
},
"prompt": {
"type": "string"
},
"category_id": {
"type": "integer"
},
"description": {
"type": "string"
},
"offset_days": {
"type": "integer"
},
"blueprint_id": {
"type": "string"
}
}
},
"description": "Ordered playbook items."
},
"link_url": {
"type": "string",
"description": "Opens the playbook in the Marcora web app."
},
"visibility": {
"type": "string"
},
"anchor_date": {
"type": [
"string",
"null"
],
"description": "Persisted YYYY-MM-DD reference date, or null."
},
"description": {
"type": "string"
}
}
}Instructions
Fetch one content playbook by id, including its full ordered list of items.
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
playbook_id |
integer | Yes | ID of the playbook to fetch |
Output: the playbook object — including its anchor_date (persisted YYYY-MM-DD reference date, or null) and link_url (opens the playbook in the Marcora web app) — with an ordered items array. Each item carries the plan fields it will stamp out (title, description, prompt, blueprint, category) plus an offset_days counted from the anchor date to compute each due date on instantiation.
Example prompts:
- "What's in my launch-week playbook?"
