Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_vse_strip

Creates a new Blender Video Sequence Editor strip (COLOR, TEXT, IMAGE, SOUND, or MOVIE) on a chosen channel and frame range, enabling timeline assembly through MCP.

Instructions

Create a new strip in the Blender Video Sequence Editor (VSE). Supports COLOR, TEXT, IMAGE, SOUND, and MOVIE strips on specified channels and frame ranges.

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": {
      "strip_type": "<strip_type>",
      "channel": "<channel>",
      "frame_start": "<frame_start>"
    },
    "name": "create_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoUnique name for the strip. Auto-generated if omitted.
textNoText string content for TEXT strips.
colorNoRGB or RGBA color float tuple (0.0 to 1.0) for COLOR strips.
channelYesSequencer channel (track) index (1 to 128).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationNoDuration in frames (used for COLOR, TEXT, and IMAGE strips).
filepathNoAbsolute or sandbox-relative file path for IMAGE, SOUND, or MOVIE strips.
request_idNo
strip_typeYesType of strip to create in the sequence editor.
frame_startYesTimeline start frame position.
approval_tokenNo

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 carries the full burden for a mutation tool. It says nothing about whether the change is undoable, what happens when a channel is already occupied, how filepath validation works, or how the approval_token/approved parameters gate execution — the schema even flags 'approved' as deprecated and untrusted, which the description never addresses.

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?

Two tight sentences, front-loaded with the action and resource, with the supported type list as the second beat. Nothing is padded or redundant.

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 12-parameter mutation tool with no annotations and no output schema, the description is thin: it omits per-type parameter requirements, the approval/request-id flow, name auto-generation behavior, and the return value. An agent could call it but would be guessing on several type-dependent combinations.

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 coverage is 75%, so the schema already documents most parameters; the description only reiterates channel and frame-range scoping and the strip type set. It adds no cross-parameter logic (e.g. which parameters are required per strip_type, or whether duration is ignored for SOUND/MOVIE), which would be the genuinely valuable addition here.

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 and resource ("Create a new strip in the Blender Video Sequence Editor") and enumerates the supported strip types, so the agent knows exactly what the tool produces. It does not distinguish itself from overlapping siblings like create_vse_text_strip or create_vse_scene_strip, which cover a subset of the same strip types.

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?

There is no guidance on when to use this generic creator versus the specialized create_vse_text_strip or create_vse_scene_strip siblings, nor any stated prerequisites (e.g. channel availability, file existence for IMAGE/SOUND/MOVIE). The agent must infer the choice from the type list alone.

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