Marcora

create_playbook_from_plans

Create a playbook by capturing existing content plans as reusable template items ("save what worked as a template"). Pass the plan UUIDs; their title / description / prompt / blueprint / category are copied into ordered playbook items.

Visibility: defaults to "team" (visible to all active teammates). Pass visibility "private" to keep it creator-only.

When to use: when the user liked a batch of plans they already produced and wants to reuse that sequence later (e.g. "turn these plans into a playbook", "save this campaign as a template"). To author a playbook from scratch, use create_playbook.

**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": {
      "plan_ids": "<plan_ids>"
    },
    "name": "create_playbook_from_plans"
  }
}

Input Schema

Name	Required	Description
`name`	No	Title for the new playbook being saved from these plans — usually the campaign or sequence they came from. Treat it as required: if it is omitted or blank the call fails with "Missing param: name". It also becomes the base of the auto-generated cycle name each time the playbook is later run.
`plan_ids`	Yes	UUIDs of existing content plans to capture as template items.
`visibility`	No	Optional. Defaults to "team". "private" keeps the playbook creator-only.
`description`	No	Optional free-text note on what this captured sequence is for and when to reuse it, shown to teammates browsing playbooks. It describes the playbook only — the captured steps keep the titles, descriptions and prompts copied from the source plans. Omitted means it is saved empty.

Output Schema

Name	Required	Description
`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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description goes well beyond them: it states exactly which plan fields are copied into items, that visibility defaults to "team", that the name becomes the base of the auto-generated cycle name on each run, and the concrete failure message when name is missing. The one gap is that idempotentHint=false is never surfaced — an agent is not warned that repeating the call with the same plan_ids produces a duplicate playbook.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then visibility, then when-to-use — a sensible order with headings that help scanning. The trailing "Links" paragraph is boilerplate about output link handling that is not specific to this tool and does not aid tool selection, so the block is slightly padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter create tool with full schema coverage, annotations, and an output schema, the description supplies everything an agent needs: trigger conditions, the sibling to use instead, the default visibility value, what data is copied, and a known error condition. Return values are correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already explains name, plan_ids, visibility, and description in depth, so the baseline is 3. The description does add one piece of meaning the schema lacks — that items become "ordered" and that plan IDs are what drive the copy — but it mostly restates the schema's field-level semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Create a playbook by capturing existing content plans as reusable template items") and immediately names the contrasting sibling create_playbook for the from-scratch case. An agent can distinguish this from create_playbook, instantiate_playbook, and produce_plan without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains an explicit "When to use" block with realistic user phrasings ("turn these plans into a playbook", "save this campaign as a template") and a clear exclusion routing to create_playbook. Both the positive trigger and the alternative are stated, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marcora tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?