Animated SVG creator & screenshot tool with CSS animation-aware capture. Render, filmstrip, and diff animated SVGs the way users actually see them.
svgshot defines 4 tools with reasonable descriptions and mostly complete schemas. Tool names are action-oriented (render, filmstrip, diff). Descriptions are adequate (100-200 chars) and explain WHAT each tool does. However, parameter descriptions are sparse or missing in several cases, and output schemas are not formally documented. Error handling is minimal, no recovery guidance or actionable error messages. The 'filmstrip' tool definition is inferred from package.json rather than explicitly visible in src/mcp.js, which caps its score. Overall: solid foundation but lacks LLM-optimization rigor around parameter clarity and error recovery.
Pixel-diff two HTML/SVG code strings. Renders both, compares pixel-by-pixel, returns difference percentage and changed pixel count.
Capture an animation as a multi-frame filmstrip. Takes N screenshots at evenly-spaced intervals and composites them into a single image strip. Perfect for visually verifying CSS animations play correctly — you can see opacity ramps, slide-ins, color transitions frame by frame.
Render HTML or SVG code to a screenshot image. Supports animation-aware capture modes: "natural" (waits for animations, default), "freeze-end" (forces animations to final state), "instant" (immediate capture at t=0).
Convenience tool for rendering raw SVG. Wraps SVG in HTML boilerplate and renders with animationMode "natural" and screenshotDelay 1000ms — perfect for capturing CSS-animated SVGs as users actually see them.
filmstrip tool definition inferred from package.json, not explicitly registered in src/mcp.js. Schema visibility is unclear; cannot verify full parameter definitions.
Output schemas not documented. Tools return image buffers or JSON objects, but LLMs cannot see the structure of returned fields (e.g., what fields does diff return? what does render return beyond a buffer?).
Error handling lacks recovery guidance. No tool description explains what to do if rendering fails, animation capture times out, or diff comparison encounters mismatched dimensions.
Parameter descriptions are minimal or missing context. E.g., 'animationMode' enum values are documented, but no guidance on when to use 'freeze-end' vs 'instant' vs 'natural'. 'screenshotDelay' lacks explanation of why 800ms is default or when to adjust.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, idempotentHint). All tools are read-only and idempotent, but this is not declared in the MCP schema, forcing LLMs to infer safety.