Skip to main content
Glama

Create a Todrawn Scribe drawing video

scribe_create_drawing
Read-onlyIdempotent

Converts SVG path line drawings into a stroke-by-stroke pen drawing video project, returning a studio link to preview and export the MP4.

Instructions

Turns a line drawing, given as SVG paths, into a Todrawn Scribe Draw project: a video of a pen drawing it stroke by stroke. Describe the subject as outlines and details, not filled shapes. Board pattern, density and the 3D camera (cameraZoom, cameraTilt, cameraRotation) are optional. Returns a link that opens the Scribe studio with the drawing loaded, where the person previews it and exports the MP4. 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": {
      "paths": "<paths>"
    },
    "name": "scribe_create_drawing"
  }
}

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".
pathsYesPaths in the order a person would draw them; the pen follows that order. y grows downward, as in SVG.
aspectNoArtboard: landscape 16:9, portrait 9:16, square 1:1, feed 4:5. Defaults to the one closest to the drawing's shape.
localeNoLanguage of the Scribe interface the link opens. Defaults to en.
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.
viewBoxNo"minX minY width height" framing the drawing, as on an <svg>. Defaults to the paths' bounding box with a margin.
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.
resolutionNoExport resolution: 720p, 1080p, 2160p. 2160p needs a Premium plan; on other plans the studio exports at 1080p instead.
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.1/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/closed-world; the description goes well beyond them by disclosing the return value (a studio link), that preview is free and account-free, that MP4 export needs a free account, and the exact Free-plan limits (5 exports per UTC day plus a 'Made with Todrawn Scribe' card) versus Premium (unlimited, optional card, 2160p and 60 fps). No contradiction with the annotations: the tool is framed as a stateless transform that returns a link.

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?

Purpose is front-loaded in the first clause, followed by input-shape guidance, optionality, and then the plan/export constraints. Every sentence carries information, though the final plan paragraph is long and reads partly as marketing copy rather than call-time guidance.

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 14-parameter tool with no output schema, the description supplies the missing pieces an agent needs: what is returned, the follow-up workflow, and the auth/plan consequences of exporting. Only speedMultiplier's effect and any failure behavior remain uncovered, which is a minor gap given the rich 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 coverage is 93%, so the schema already explains nearly every parameter in depth, and the description only restates that board pattern, density and the 3D camera are optional. The outline-not-filled guidance echoes what the schema already says about fills being ignored. speedMultiplier is undocumented in both places, so the description does not compensate for the residual gap.

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?

States a precise verb and transformation: it 'Turns a line drawing, given as SVG paths, into a Todrawn Scribe Draw project: a video of a pen drawing it stroke by stroke.' The SVG-path input requirement implicitly separates it from raster-based siblings like scribe_paint_image, but no sibling is named or contrasted explicitly.

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?

Gives clear operating guidance: describe subjects as outlines and details rather than filled shapes, and notes which parameters are optional. It also lays out the workflow (open the returned link, preview, then export) with the conditions attached to each stage. It stops short of saying when to choose this over scribe_create_video or scribe_paint_image.

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