Marcora

get_playbook

Read-onlyIdempotent

Fetch one content playbook by id, including its full ordered list of items.

When to use: to inspect a playbook before instantiating or editing it, or when the user asks about the contents of a specific saved playbook/template.

NotFound also covers a teammate's PRIVATE playbook (visibility='private', caller is not the creator) — do not retry.

**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": {
      "playbook_id": "<playbook_id>"
    },
    "name": "get_playbook"
  }
}

Input Schema

Name	Required	Description	Default
`playbook_id`	Yes	Numeric id of the playbook to fetch — the `id` returned by list_playbooks, create_playbook or a previous get_playbook, and the trailing number in the playbook's link_url. It is a plain integer, not a UUID; a non-integer value is rejected. Only playbooks in your current team are reachable, and an unknown id, another team's playbook, or a teammate's private playbook all come back as NotFound.

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.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior beyond them: the conflation of NotFound with private visibility and the instruction not to retry. It also imposes an output-handling contract (copy link_url character for character, never rebuild it), which annotations cannot express.

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 usage, then output-handling caveats, with no filler sentences. Minor redundancy in repeating the NotFound/private case that the parameter schema already documents.

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?

An output schema exists, so return values needn't be explained; the description instead covers id provenance, team scoping, error meaning, and link handling. For a single-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the playbook_id description already covers integer type, id provenance, team scoping, and NotFound cases, so the description adds little beyond what the schema provides. The private-playbook NotFound note is the main addition and is largely mirrored in the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Fetch one content playbook by id") plus the return scope ("including its full ordered list of items"), which distinguishes it from the list_playbooks sibling. An agent knows immediately this is a single-resource read, not an enumeration.

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?

Gives explicit when-to-use framing ("to inspect a playbook before instantiating or editing it, or when the user asks about the contents of a specific saved playbook/template"), which routes the agent away from instantiate_playbook/update_playbook. It also supplies a when-not/error path: NotFound also means a teammate's private playbook, so do not retry.

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?