Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

render_vse_sequence

Render the active Video Sequence Editor timeline to a video or image sequence at a specified output path, with optional format, codec, frame range, FPS, and resolution settings.

Instructions

Render a video or image sequence from the active Video Sequence Editor (VSE) timeline to an output file on disk using FFMPEG or image formats.

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": {
      "output_path": "<output_path>"
    },
    "name": "render_vse_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoTimeline framerate for rendering.
formatNoContainer format (defaults to MPEG4).MPEG4
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
frame_endNoOptional ending frame (defaults to scene frame_end).
request_idNo
audio_codecNoAudio encoding codec (defaults to AAC).
frame_startNoOptional starting frame (defaults to scene frame_start).
output_pathYesDestination file path for the rendered video or image sequence (path traversal forbidden).
video_codecNoVideo encoding codec (defaults to H264 for MPEG4/MKV, PRORES for QUICKTIME).
resolution_xNoHorizontal render resolution in pixels.
resolution_yNoVertical render resolution in pixels.
approval_tokenNo
resolution_percentageNoRender resolution scaling percentage (1 to 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the whole behavioral burden and it does not: nothing about this being a long-running/blocking write, whether existing files at output_path are overwritten, permission requirements, or how failures are surfaced. It notes the underlying backend (FFMPEG/image formats) but that is closer to implementation detail than agent-relevant behavior.

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 no filler. It could earn its place slightly better by adding one clause on distinguishing it from render_scene, but nothing is wasted.

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

Completeness2/5

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

For a 14-parameter, non-read-only tool that writes files to disk with no output schema and no annotations, the single sentence is thin. An agent cannot learn from it what is produced (single file vs image sequence directory), how long it takes, or what happens on partial failure.

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 79%, effectively at the baseline where the schema does the heavy lifting for codecs, resolution, and frame range. The description adds only that rendering uses "FFMPEG or image formats", which loosely motivates the video/audio codec enums, but nothing about the approval-related fields or frame defaults beyond the schema text.

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 specific verb ("Render") plus the resource ("video or image sequence from the active Video Sequence Editor (VSE) timeline") and the effect ("to an output file on disk"). The VSE-timeline qualifier implicitly separates it from a scene renderer like render_scene, though the sibling is never named.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no naming of alternatives such as render_scene or inspect_render_output, and no stated prerequisites (an active timeline with strips, configured settings). The phrase "active VSE timeline" is the only implicit condition, so an agent must infer the rest.

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