Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

modify_vse_strip

Update an existing Blender VSE strip to change its channel, start frame, duration, mute or lock state, blend mode, or color.

Instructions

Modify an existing strip in the Blender Video Sequence Editor (VSE). Allows updating channel, start frame, duration, mute, lock, blend mode, and color.

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

Input Schema

NameRequiredDescriptionDefault
lockNoLock state against accidental editing.
muteNoMute (hide/disable) state.
nameYesName of the strip to modify.
colorNoRGB color float tuple (0.0 to 1.0) for COLOR strips.
channelNoNew sequencer channel index (1 to 128).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationNoNew duration in frames.
new_nameNoOptional new name for the strip.
blend_typeNoBlend mode (e.g., REPLACE, CROSS, ALPHA_OVER).
request_idNo
blend_alphaNoBlend opacity (0.0 to 1.0).
frame_startNoNew timeline 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: it says 'Modify' but never states whether changes are reversible/undoable, whether the strip must already exist, what happens if 'name' matches nothing, or what is returned. It also ignores the unusual approval_token/task_id/approved parameters (the schema flags 'approved' as deprecated and untrusted), which an agent would want explained at the tool level.

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?

Two short sentences, with the identity of the tool front-loaded. The field enumeration is a mild redundancy against the schema, but it is compact and not padded.

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 mutation tool with no annotations and no output schema, the description leaves significant gaps: naming/rename semantics, approval flow, failure behavior for a missing strip, and partial-update semantics (are unspecified fields left unchanged?) are all unaddressed.

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%, so the schema already documents most parameters with ranges and examples (channel 1-128, blend modes REPLACE/CROSS/ALPHA_OVER). The description only re-lists a subset of fields without adding meaning, and says nothing about new_name vs. the required name identifier or the approval-related parameters.

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 names a specific verb ('Modify') and resource ('an existing strip in the Blender Video Sequence Editor'), and enumerates the editable properties. It is clear what the tool does, though it does not differentiate itself from siblings such as trim_vse_strip or transform_vse_strip, which plausibly overlap on duration/frame_start.

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 statement of when to use this tool instead of trim_vse_strip, crop_vse_strip, transform_vse_strip, or reorder_vse_strips, despite obvious overlap in the listed fields. No preconditions (strip must exist, scene context, active sequence) are given.

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