stykanimate-mcp

render_and_export_media

Render a stick figure animation to MP4, GIF, WebM, SVG, PNG or SVG sequences, or an interactive HTML player with configurable resolution and frame rate.

Instructions

Renders and exports the active stick figure animation to visual media formats: "mp4" (H.264 video), "gif" (palette-optimized animated GIF), "webm" (VP9 video), "svg" (single frame vector), "animated-svg" (standalone self-playing vector), "png-sequence" (folder of crisp PNG frames), "svg-sequence" (folder of SVGs), or "html-player" (interactive standalone 60fps web player with timeline scrubber controls).

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": {
      "outputPath": "<outputPath>",
      "format": "<format>"
    },
    "name": "render_and_export_media"
  }
}

Input Schema

Name	Required	Description
`fps`	No	Playback frame rate (defaults to document fps)
`loop`	No	Whether to loop video/GIF animation indefinitely (default: true)
`width`	No	Output width in pixels (defaults to canvas width)
`format`	Yes	Export format: "mp4", "gif", "webm", "svg", "animated-svg", "png-sequence", "svg-sequence", or "html-player"
`height`	No	Output height in pixels (defaults to canvas height)
`frameIndex`	No	Single frame index to render when format is "svg" (default: 0)
`outputPath`	Yes	Output file or directory path (e.g. "./renders/battle.mp4", "./stick.gif", "./preview.html", or "./frames")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 3, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it only covers output characteristics (codec choices, palette optimization, 60fps player). It says nothing about whether outputPath overwrites existing files, whether a document must be active/open, whether the render is long-running or blocking, or what is returned on success. "Active" is the only hint at a precondition, and it is not elaborated.

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?

A single front-loaded sentence with the action first and the format catalog second; no filler. The parenthetical glosses on each format are dense but each earns its place by disambiguating svg from animated-svg and png-sequence from svg-sequence.

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

Completeness3/5

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

For a 7-parameter, no-annotation, no-output-schema mutation-style tool, the description covers the format dimension well but leaves the file-writing semantics and return value unaddressed. An agent still lacks what it needs to know about overwrite risk and success confirmation before calling it.

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 the baseline is 3; the description earns above that by explaining what each enum value actually produces (single-frame vector vs. self-playing vector vs. folder of frames), which the schema's format field merely restates. It still doesn't clarify how width/height interact with defaults or what outputPath means for the sequence formats beyond the schema's own examples.

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 pair ("Renders and exports") and a specific resource ("the active stick figure animation") and enumerates every supported output format. No sibling tool does export, and the enumeration makes it unmistakable versus compile_and_save_project or generate_motion_sequence.

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

Usage Guidelines3/5

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

Usage is implied by the format list, and the schema note tying frameIndex to "svg" hints at per-format behavior, but the description never says when to pick this over compile_and_save_project or which format suits which downstream need. No explicit exclusions or prerequisites are stated.

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

Deploy Server