Skip to main content
Glama

add_sequencer_strip

Add a text, solid color, or movie strip to Blender's video sequencer at a chosen channel and frame range, enabling titles, background fills, and video clips in a sequence.

Instructions

Add a text, solid colour or movie strip to the video sequencer.

Higher channels draw on top. Style text or move any strip afterwards with set_strip_property; fade it with add_strip_fade.

Args: kind: TEXT (a title), COLOR (a solid background) or MOVIE (a video file). name: Strip name; defaults to the kind or the file name. channel: 1 to 128. frame_start: First frame. length: Frames, for TEXT and COLOR (a MOVIE takes the file's length). text: TEXT only: the words, up to 2000 characters. font_size: TEXT only, 1 to 2000. color: TEXT: RGB(A) of the letters; COLOR: RGB of the fill. 0.0 to 1.0. filepath: MOVIE only: absolute path to .mp4, .mov, .mkv, .webm, .avi or .m4v.

Returns: Dict with the strip's name, type, channel and frame range.

Input Schema

NameRequiredDescriptionDefault
kindYes
nameNo
textNo
colorNo
lengthNo
channelNo
filepathNo
font_sizeNo
frame_startNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses layering behavior and that MOVIE strips take the file's length, but it does not cover permissions, side effects, failure modes, or whether the sequencer must already exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, behavioral notes are brief, and the Args/Returns structure makes the detailed parameter documentation easy to scan. Every sentence contributes useful information.

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

Completeness5/5

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

For a 9-parameter creation tool with no annotations and no schema descriptions, the definition supplies all parameter semantics, return shape, channel layering, and media-specific behavior. An output schema exists, so return values are adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: every parameter is explained with applicable ranges, type-specific meanings, defaults, units, and file format constraints.

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?

The description states a specific verb and resource: adding text, solid color, or movie strips to the video sequencer. The kinds make the tool's scope clear, though it does not explicitly differentiate itself from close siblings such as add_image_sequence_strip or add_sound_strip.

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?

It gives useful usage context by explaining that higher channels draw on top and by directing follow-up styling/movement to set_strip_property and fading to add_strip_fade. It does not explicitly state when to use this tool instead of related strip-creation siblings.

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