proofcut

Overview Schema Source Related Servers Discussions Admin

graphic_new

DestructiveIdempotent

Create an animated graphic from a template or custom HTML, captured frame by frame. Define intro, hold, and outro phases to place it as a timed overlay in a video.

Instructions

Make an animated graphic — a web page, captured frame by frame — from a template or your own HTML.

A graphic has three phases, in seconds of the page's own timeline: an intro that plays once from the start of wherever it is placed, a hold that fills whatever the span leaves (the page's last intro frame, or loop seconds repeated), and an outro that plays once to end the span. The span decides the length, never the graphic, so cuts cannot break it. Write the page's outro animations to start where the intro ends (after one loop, if it loops). Nothing on the page may load from the network.

Place it with overlay_add(graphic=name). Then look at it with graphic_sheet. The capture draws at the project's canvas and export rate; changing either makes it stale, and export refuses a stale graphic.

Input Schema

Name	Required	Description
`html`	No	A whole page, written by hand. CSS animations and transitions are seeked frame by frame, and requestAnimationFrame, performance.now and Date follow the seek; a script on timers must define window.proofcutSeek(seconds). Fonts load from /_proofcut/fonts/static/Outfit-Regular.ttf and Outfit-Bold.ttf; nothing loads from the network.
`loop`	No	Seconds of the page after the intro to repeat through the hold, for a hold that moves (a blinking caret). Unset, the hold is the page's last intro frame, still; a page still moving there is refused.
`name`	Yes	The graphic's name: lowercase letters, digits, - and _. overlay_add places it by this name.
`path`	No	The project directory to act on. Omit it — the usual case — when this server is bound to a project (started as `proofcut -C DIR mcp`, or inside a project; `ping` says which): it then resolves to that one bound project, a relative path resolves against it, and a path outside it is refused by name. Unbound, `path` is the whole address and omitting it refuses rather than guessing.
`intro`	No	Seconds of the page that play once from the start of the span.
`outro`	No	Seconds of the page, from the hold on, that play once to end the span.
`pages`	No	Browser pages capturing side by side, 1 to 8. Default 2.
`slots`	No	The template's slots, as text. A colour is #rrggbb, a number a number.
`capture`	No	Capture it now. False writes the page and draws nothing.
`replace`	No	Replace a graphic of this name. Unset, an existing one is refused.
`template`	No	A template to fill (graphic_templates lists them). One of template or html.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.44.0Oct 1, 2026

changedInput schema / properties / html / description

Previous value: -"A whole page, written by hand. CSS animations and transitions are seeked frame by frame; a script animating from its own clock must define window.proofcutSeek(seconds). Fonts load from /_proofcut/fonts/static/Outfit-Regular.ttf and Outfit-Bold.ttf; nothing loads from the network."New value: +"A whole page, written by hand. CSS animations and transitions are seeked frame by frame, and requestAnimationFrame, performance.now and Date follow the seek; a script on timers must define window.proofcutSeek(seconds). Fonts load from /_proofcut/fonts/static/Outfit-Regular.ttf and Outfit-Bold.ttf; nothing loads from the network."

Addedv0.43.0Sep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description explains the three-phase timeline model, how intro/hold/outro interact with the span, the loop behavior, the network restriction, and the staleness rule tied to canvas/export rate changes. It also clarifies that an existing graphic is refused unless replace is set, adding important behavioral context beyond the destructiveHint annotation.

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 description is front-loaded with the core purpose and then organized into a phase model followed by placement/inspection guidance. It is somewhat long, but each paragraph carries useful information, and there is little redundancy given the complexity of the tool.

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?

The tool is complex, with many parameters, but the description covers the essential conceptual model and operational constraints. An output schema exists, so return-value details are not needed, and the schema already documents parameters thoroughly.

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 100%, so parameter-level details are already well documented. The description adds conceptual meaning by explaining how intro, hold, outro, and loop form the graphic's timeline and how the span controls length, which is not obvious from the individual schema entries 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?

The description opens with a specific verb and resource: 'Make an animated graphic — a web page, captured frame by frame — from a template or your own HTML.' It distinguishes the tool from siblings by explaining the creation workflow and explicitly pointing to overlay_add and graphic_sheet for placement and inspection.

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?

The description gives clear context for when to use it: creating an animated graphic from a template or custom HTML, then placing and viewing it. It does not explicitly state when not to use it or name alternatives like graphic_edit or graphic_capture, so it falls short of full alternative-routing guidance.

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

Deploy Server