MCP Tools
Plans & Playbooks

create_playbook

Create a reusable content playbook — an ordered template of content-plan items you can stamp out as a batch.

Input Schema

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Playbook name."
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Ordered playbook items (each becomes one plan on instantiation)."
    },
    "visibility": {
      "type": "string",
      "description": "\"team\" (default) or \"private\"."
    },
    "anchor_date": {
      "type": "string",
      "description": "Optional YYYY-MM-DD reference date the playbook is built around (a launch, event, campaign kickoff). Persisted on the playbook; each item's offset_days counts from it, and it becomes the default anchor when instantiating. Leave off for an evergreen/undated template."
    },
    "description": {
      "type": "string",
      "description": "Free-text description."
    }
  }
}

Output Schema

{
  "type": "object",
  "properties": {
    "link_url": {
      "type": "string",
      "description": "Opens the playbook in the Marcora web app."
    },
    "anchor_date": {
      "type": [
        "string",
        "null"
      ],
      "description": "Persisted YYYY-MM-DD reference date, or null."
    }
  },
  "description": "The created playbook object, including its persisted anchor_date (YYYY-MM-DD or null) and a link_url that opens it in the Marcora web app."
}

Instructions

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. To build a playbook from plans you already ran, use create_playbook_from_plans instead.

Parameters:

Parameter Type Required Description
name string Yes Playbook name
description string No Free-text description
visibility string No team (default) or private
anchor_date string No Optional YYYY-MM-DD reference date the playbook is built around (a launch, event, campaign kickoff). Persisted on the playbook; each item's offset_days counts from it, and it becomes the default anchor when instantiating. Leave off for an evergreen/undated template
items array No Ordered playbook items (each becomes one plan on instantiation)

Output: the created playbook object, including its persisted anchor_date (or null) and a link_url that opens the new playbook in the Marcora web app — share it with the user.

Example prompts:

  • "Make me a launch-week playbook"
  • "Save this sequence as a template"
Scroll to Top