Skip to main content
Glama
Sign In
GehDoc

svg-to-video

by GehDoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

render_svg_to_video

Converts animated SVG from code or file into MP4, WebM, MKV, MOV, aPNG, or GIF with transparency and Base64 delivery.

Instructions

Render an animated SVG (from raw SVG code or file path) into a high-quality video (MP4, WebM, MKV, MOV) or animated image (aPNG, GIF) with in-band Base64 media delivery. Use this tool when you need to convert animated SVG graphics into video or image files. First use inspect_svg_animation to detect duration and dimensions if unknown. Specify svgContent for raw XML input or svgFilePath for local files. Pass transparent: true for WebM/GIF/aPNG transparency.

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (e.g. 24, 30, 60). Default: 60.
holdNoSeconds to freeze the last frame at the end of the video.
scaleNoScale factor (1-4) when using original resolution. Default: 1.
formatNoOutput media format. Defaults to webm if transparent is true, otherwise mp4.
outDirNoOutput directory to preserve generated file locally. Omit to deliver purely in-band via ephemeral storage (forbidden in hosted sandboxed mode).
bgColorNoBackground color hex code (e.g. #ffffff). Cannot be used with transparent.
durationNoDesired animation duration in seconds. If omitted, duration is auto-detected.
resolutionNoResolution preset. Default: original.original
svgContentNoRaw SVG string content to render (required if svgFilePath is not provided).
svgFilePathNoAbsolute or relative path to the input .svg file (forbidden in hosted sandboxed mode).
transparentNoRender with full alpha-channel transparency (supported for webm, gif, apng, mov).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.28.0
    • changedInput schema / properties / outDir / description
      Previous value: -"Output directory for the generated media file. Defaults to current working directory."New value: +"Output directory to preserve generated file locally. Omit to deliver purely in-band via ephemeral storage (forbidden in hosted sandboxed mode)."
    • changedInput schema / properties / svgContent / description
      Previous value: -"Raw SVG string content to render (if svgFilePath is not provided)."New value: +"Raw SVG string content to render (required if svgFilePath is not provided)."
    • changedInput schema / properties / svgFilePath / description
      Previous value: -"Absolute or relative path to the input .svg file."New value: +"Absolute or relative path to the input .svg file (forbidden in hosted sandboxed mode)."
  2. First observedv0.27.8

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses in-band Base64 media delivery, the ephemeral-vs-local outDir tradeoff, format-dependent transparency support, and the auto-detection of duration. It omits cost/latency characteristics and failure behavior, which keeps it from a 5.

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?

Four tight sentences with the core verb and output formats front-loaded, then usage, prerequisites, and input-selection rules. No filler, though the final sentence is largely redundant with schema text.

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 an 11-parameter tool with no annotations and no output schema, the description covers the essential decision points: input source, output format, transparency, and delivery mode. Defaults and per-format constraints live in the schema, but nothing about error handling or resource limits is addressed.

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 description coverage is 100%, so the baseline is 3. The description only restates the svgContent-vs-svgFilePath selection and the transparent flag guidance, both of which the schema already documents; it adds no new syntax, ranges, or interaction rules.

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 and resource ('Render an animated SVG ... into a high-quality video ... or animated image') and enumerates concrete output formats (MP4, WebM, MKV, MOV, aPNG, GIF). It also distinguishes itself from its only sibling by noting inspect_svg_animation is for detection, not conversion.

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 an explicit trigger ('Use this tool when you need to convert animated SVG graphics into video or image files') and a prerequisite/alternative step ('First use inspect_svg_animation to detect duration and dimensions if unknown'). No explicit when-not guidance beyond the sibling pointer, so it falls short of a 5.

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

Deploy Server

Other Tools