Skip to main content
Glama

blender_vse

Manage video strips, apply transitions, trim, cut, and render videos in Blender's Video Sequence Editor through a unified interface.

Instructions

PORTMANTEAU PATTERN RATIONALE: Consolidates 20 VSE operations into a single interface. Prevents tool explosion while providing full video editing: strip management, timeline editing, effects, and rendering. Follows FastMCP 3.x best practices.

Blender's built-in Video Sequence Editor (VSE) exposed as MCP tools. Add video/audio/image strips, apply transitions, trim, cut, move, and render to video.

Strip Creation (7 operations):

  • add_movie: Add a video/MP4 file as a movie strip

  • add_sound: Add an audio file (WAV, MP3, etc.) as a sound strip

  • add_image_sequence: Add a folder of images as an image sequence strip

  • add_scene: Add a 3D scene as a strip (compositing)

  • add_color: Add a solid color matte strip

  • add_text: Add a text overlay strip

  • add_effect: Add a transition/filter effect between strips

Strip Editing (6 operations):

  • delete_strip: Remove a strip by name

  • cut_strip: Cut a strip at a specific frame

  • trim_strip: Set strip start/end frames (trim handles)

  • move_strip: Move a strip to a different channel or frame

  • mute_strip: Mute or unmute a strip

  • lock_strip: Lock or unlock a strip

Properties (3 operations):

  • set_speed: Change playback speed (creates speed effect strip)

  • set_blend: Set blend mode and opacity (ALPHA_OVER, CROSS, ADD, etc.)

  • set_transform: Set position, scale, rotation of a strip

Information (2 operations):

  • list_strips: List all strips in the timeline with properties

  • get_timeline_info: Get timeline frame range, FPS, strip count, channels

Rendering (1 operation):

  • render_video: Render the VSE timeline to a video file (H264/MPEG4)

Cleanup (1 operation):

  • clear_vse: Remove all strips from the timeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe VSE operation to perform.list_strips
filepathNoPath to video or audio file. Required for: add_movie, add_sound.
directoryNoDirectory path for image sequences. Required for: add_image_sequence.
strip_nameNoTarget strip name for editing operations. Required for most edit ops.
strip1_nameNoFirst strip name for effect creation. Required for: add_effect.
strip2_nameNoSecond strip name for effect creation. Required for: add_effect.
channelNoVSE channel number (higher = on top). Default: 1.
frameNoFrame number for placement/cutting. Default: 1.
lengthNoStrip duration in frames. Default: 120. Used for: add_color, add_text, add_effect.
frame_startNoStart frame for trim or render range. Default: 1.
frame_endNoEnd frame for render range. Default: 250.
textNoText content. Required for: add_text.
font_sizeNoFont size in points. Default: 48. Used for: add_text.
color_rNo
color_gNo
color_bNo
effect_typeNoEffect type. Options: CROSS, WIPE, GLOW, TRANSFORM, SPEED, ADJUSTMENT, GAUSSIAN_BLUR, TEXT, COLOR, MULTICAM. Default: CROSS.CROSS
cut_typeNoCut type. SOFT (preserves handles) or HARD (snaps). Default: SOFT.SOFT
muteNoTrue to mute, False to unmute. Default: True. Used for: mute_strip.
lockNoTrue to lock, False to unlock. Default: True. Used for: lock_strip.
speed_factorNoPlayback speed multiplier. 2.0 = double speed, 0.5 = half speed. Default: 1.0.
blend_typeNoBlend mode. Options: ALPHA_OVER, CROSS, ADD, SUBTRACT, MULTIPLY, SCREEN, OVERLAY, DARKEN, LIGHTEN, etc. Default: ALPHA_OVER.ALPHA_OVER
blend_alphaNoOpacity 0.0-1.0. Default: 1.0.
position_xNo
position_yNo
scale_xNo
scale_yNo
rotationNoStrip rotation in degrees. Used for: set_transform.
scene_nameNoSource 3D scene name. Required for: add_scene.
fit_methodNoHow to fit media. FIT (maintains aspect), FILL (crops), STRETCH. Default: FIT.FIT
include_audioNoInclude audio track from video. Default: True. Used for: add_movie.
resolution_xNo
resolution_yNo
output_pathNoOutput file path (.mp4 recommended). Required for: render_video.
containerNoVideo container format. Options: MPEG4, AVI, QUICKTIME, OGG, MKV. Default: MPEG4.MPEG4
codecNoVideo codec. Options: H264, H265, THEORA, AV1. Default: H264.H264
qualityNoEncoding quality. Options: BEST, GOOD, MEDIUM. Default: MEDIUM. Used for: render_video.MEDIUM
fpsNoFrames per second. Default: 30. Used for: render_video.
audio_codecNoAudio codec. Options: AAC, MP3, PCM, VORBIS, FLAC. Default: AAC. Used for: render_video.AAC
audio_bitrateNoAudio bitrate in kbps. Default: 192. Used for: render_video.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations present, so description carries full burden. Lists each operation with brief behavior descriptions (e.g., 'cut_strip: Cut at a specific frame'). Some details on required parameters per operation. However, lacks discussion of side effects, errors, or resource usage.

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?

Well-structured with introduction, then grouped lists. Every sentence adds information, but length is high (multiple paragraphs). Front-loaded with purpose, but could be more concise.

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?

Complex tool with 40 parameters and 20 sub-operations. Description covers all operations and parameter contexts. Output schema exists, so return values not needed. Lacks examples or edge cases, but sufficient for operation selection.

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 78%, so baseline is 3. Description adds context by mapping parameters to operations (e.g., 'Required for: add_movie, add_sound'), but does not significantly expand on parameter meaning beyond schema.

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?

Clearly states it consolidates 20 VSE operations into one interface, with lists categorized by strip creation, editing, properties, info, rendering, cleanup. Uses specific verbs and differentiates from sibling tools like blender_render and blender_animation.

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?

Mentions preventing tool explosion but does not explicitly guide when to use this over alternatives (e.g., blender_animation for animation, blender_render for rendering). Implies use for VSE editing, but lacks direct comparisons or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server