Skip to main content
Glama

MakersMCP playbooks

makersmcp_playbook
Read-onlyIdempotent

Read step-by-step playbooks for MakersMCP jobs before multi-step tasks or when unsure which tool fits; each topic gives call order, key arguments, checks, and handover details.

Instructions

Returns MakersMCP's playbooks. Each covers one kind of job for the kits on this server: the order of calls, the arguments that matter, what to check and what to hand over. Before a job with more than one step, like a launch film, music fitted to a video or a launch kit, or when unsure which tool fits a request, read its topic and wait for it before any other call: the topic can change the job's first call. Each topic is complete for its job, and up to three can be read in one call. Topics:

  • getting-started: which tool fits which request, how jobs, waits and files work, and what the kits do not make

  • launch-kit: the files a launch needs, made in order across the kits, with the place map and what to hand over

  • brand: make_brand_kit: logo files, colors, fonts, first screen, store assets and the site's own claims

  • fonts: make_font_kit: the fonts a page draws with, their files and licenses, the closest free fonts

  • screenshots: take_screenshots and check_pwa_screenshots: pages, store and gallery sizes, themes, manifest screenshots

  • demo-video: record_demo_video: a tour or a steps file, the timing in steps.json, what comes after

  • launch-film: make_launch_film, plan_launch_film, render_launch_film, make_launch_stills: the film and its pictures

  • film-json: film.json, the plan of a launch film: clips, scene types, the words on screen and their rules

  • checks: check_video: what to expect of each video, cuts on the beat, reading CHECK.md and the sheet

  • music: analyze_music and fit_music: a track fitted to a film or a demo and laid under it, the hit, a voice

  • reframe: reframe_video, plan_reframe and check_place_limits: each place's shape, length and size, the crop, the checks

  • captions: caption_video, make_subtitles, list_caption_styles: captions in the brand's fonts, subtitle files, app margins

  • jobs-and-files: long jobs, calls that end early, cancelling, folders, passing one job's files to the next

  • troubleshooting: setup, the errors the tools return and their fixes, the kits' flag names

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": {
      "topics": "<topics>"
    },
    "name": "makersmcp_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicsYesOne to three topics from this tool's list, like ["launch-film"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds behavior the annotations cannot: that a topic can change the job's first call, that each topic is complete for its job, and that up to three topics may be read in one call. It stops short of describing the shape or size of the returned text, which is the one remaining behavioral gap.

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?

The routing rule and sequencing warning are front-loaded before the long topic catalog, which is the right order. The catalog is long and a few entries are terse to the point of opacity ("the hit, a voice"), but each line maps a topic to concrete tools or artifacts and none is pure filler.

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 single-parameter, no-output-schema routing tool on a 22-tool server, the definition covers the decision (when to read, which topic), the mechanics (one to three topics per call), and the consequence (the topic can change the first call). Nothing an agent needs in order to invoke it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% and the enum already lists the 14 topic names, but the description explains what each enum value actually contains (e.g. "reframe: reframe_video, plan_reframe and check_place_limits: each place's shape, length and size"), which the schema does not. That content map is genuine meaning an agent cannot get from the enum alone.

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 ("Returns MakersMCP's playbooks") and immediately defines what a playbook is: "the order of calls, the arguments that matter, what to check and what to hand over." The topic list makes the boundary with every sibling tool explicit, so an agent can distinguish it from make_launch_film or check_video without opening any other 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?

Gives an explicit when-to-use rule with a threshold ("Before a job with more than one step... or when unsure which tool fits a request") plus concrete examples (launch film, music fitted to a video, launch kit). It also states a hard sequencing constraint — read the topic and wait before any other call — which is exactly the guidance an agent needs to order its calls.

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