Skip to main content
Glama

Create a Todrawn Scribe video

scribe_create_video
Read-onlyIdempotent

Turn code or text into a handwritten-pen video project and get a link to preview it and export the MP4 in the studio.

Instructions

Turns code or text into a Todrawn Scribe project: a video of a pen writing it out by hand. Returns a link that opens the Scribe studio with the project loaded, where the person previews it and exports the MP4. Optional segments give chosen passages their own speed, size, pen, pause or zoom; pattern and density set the board; cameraZoom, cameraTilt and cameraRotation set the 3D camera. Give the link to the person; do not try to download a video from it. Previewing is free and needs no account. Exporting the MP4 needs a free Todrawn account: the Free plan allows 5 exports per UTC day and ends each video with a "Made with Todrawn Scribe" card; Premium has unlimited exports, makes the card optional and also exports 2160p (4K) and 60 fps.

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": {
      "text": "<text>"
    },
    "name": "scribe_create_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoExport frame rate: 24, 30, 60. 60 needs a Premium plan; on other plans the studio exports at 30 fps instead.
penNoPen for the whole video: ballpoint (default), marker, fineliner, pencil or chalk. Chalk draws a grainy chalk line and is meant for background: "dark".
textYesThe code or text to draw, exactly as it should appear.
aspectNolandscape 16:9 (default), portrait 9:16 for Shorts/Reels/TikTok, square 1:1, feed 4:5.
layoutNoauto scrolls tall aspects and pages wide ones.
localeNoLanguage of the Scribe interface the link opens. Defaults to en.
timingNoreading: paced by words per second (default); pen: paced by pen travel.
densityNoSpacing of the board pattern's marks, 16 to 192, even numbers only (default 28). Larger is sparser.
patternNoMarks printed on the board behind the writing: dots, lines, grid, staff, vertical lines or blank.
languageNoSyntax colouring: js, ts, py, java, clike, sql, html, css, bash, go, rust, plain. Common names (typescript, python, c++, shell, markdown) are accepted. Defaults to plain.
markdownNoInterpret Markdown in plain text (default true).
segmentsNoPassages with their own speed, size, pen, pause or zoom, for example to slow down the key line. Each one selects text with match or fromLine/toLine and sets at least one of speed, size, pen, pauseAfter, zoom. At most 500; later ones win where they overlap.
colorModeNosyntax colours per token, or one solid ink colour.
backgroundNodark board or light paper.
cameraTiltNoCamera angle above the board in degrees: 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90. 40 is the standard view, lower is flatter and shows more depth, 90 looks straight down. Applies to the 3D pen view only (its preview and its export); the flat 2D view ignores it.
cameraZoomNoCamera framing of the 3D pen view (its preview and its export) in percent: 75, 100, 125, 150, 175, 200; 75 shows the most board, 200 follows the pen closest. The flat 2D view ignores it. Not the same as a passage's zoom.
readingWpsNoWords per second when timing is reading.
resolutionNoExport resolution: 720p, 1080p, 2160p. 2160p needs a Premium plan; on other plans the studio exports at 1080p instead.
solidColorNoInk colour as #rrggbb when colorMode is solid.
cameraRotationNoCamera rotation around the board in degrees: -45, -40, -35, -30, -25, -20, -15, -10, -5, 0, 5, 10, 15, 20, 25, 30, 35, 40, 45. 0 looks straight on, negative moves the camera to the left of the board, positive to the right. Applies to the 3D pen view only (its preview and its export); the flat 2D view ignores it.
speedMultiplierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses what the call actually yields (a studio link, not a file), that preview is free and accountless, the 5-exports-per-UTC-day Free cap, the forced 'Made with Todrawn Scribe' card, and the Premium-only 4K/60fps/optional-card behavior. Those quota and plan-gating details are exactly the operational context an agent needs before calling.

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?

It is front-loaded with purpose and return value, then parameter groups, then the hand-off instruction and plan limits, with no filler sentences. The final plan paragraph is dense but every clause (quota, watermark, 4K, 60fps) carries decision-relevant information.

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

Completeness4/5

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

For a 21-parameter tool with no output schema, the description covers what is returned (a link), what the recipient does with it, and the account/quota constraints, which is the critical missing piece structured fields cannot supply. Only minor gaps remain, such as the undocumented speedMultiplier and no note on validation failures.

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

Parameters4/5

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

Schema coverage is 95%, so the baseline is 3, but the description adds orientation across 21 parameters by grouping them conceptually: segments for per-passage speed/size/pen/pause/zoom, pattern and density for the board, and the three camera parameters for the 3D view. It does not explain speedMultiplier or the fps/resolution plan fallbacks in prose, leaving that to the schema.

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

Purpose4/5

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

The first sentence gives a specific verb and resource — turns code/text into a Todrawn Scribe project rendered as a hand-writing pen video — and states the artifact produced (a studio link). It is clearly distinct from a drawing tool by resource, but it never names or contrasts a sibling explicitly, so it stops short of the top band.

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

Usage Guidelines4/5

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

It gives an explicit do/don't for the follow-up step: hand the link to the person and do not attempt to download a video from it. It also establishes the preview-vs-export split and the account requirement for export, but it offers no routing to alternative tools for other output types.

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