Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_vse_scene_strip

Create a nested scene strip in the active VSE to reference another Blender scene's 3D camera view or sequencer timeline, enabling compositing and timeline reuse.

Instructions

Create a nested SceneStrip referencing another Blender scene's 3D camera view or sequencer timeline inside the active VSE.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional custom name for the scene strip.
channelYesTimeline channel index (1 to 128).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationNoOptional strip duration in frames (defaults to scene frame range length).
blend_typeNoBlend mode for compositing the scene strip.
request_idNo
scene_nameYesName of the referenced Blender scene (must exist in bpy.data.scenes).
view_layerNoOptional view layer name in the referenced scene.
blend_alphaNoOpacity factor (0.0 to 1.0).
frame_startYesStarting frame on the timeline.
scene_inputNoInput source from referenced scene: 'CAMERA' (render 3D camera) or 'SEQUENCER' (nested sequencer timeline).CAMERA
scene_cameraNoOptional camera object name to use from the referenced scene.
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 disclosure burden, and it reveals little beyond the creation act itself. It does not state that the active VSE/sequence editor must already exist, that scene_name must resolve to a real scene, what happens on name collisions, or whether the operation is reversible.

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 that wastes no words and puts the key noun (nested SceneStrip) and target context (active VSE) up front. It is dense but readable; no restatement or filler.

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?

With 14 parameters, no annotations, and no output schema, a one-sentence description is thin. It omits preconditions, side effects on the active sequence editor, and what the tool returns (e.g., a strip identifier), which an agent needs before invoking a mutation of this complexity.

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 including scene_input's CAMERA/SEQUENCER enum and the deprecated approved flag. The description adds only conceptual framing about what the nested strip represents, no format, default, or interaction detail beyond the schema.

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: 'Create a nested SceneStrip' referencing another Blender scene's CAMERA view or SEQUENCER timeline inside the active VSE. This distinguishes it from the generic create_vse_strip sibling by specifying the nested-scene semantics, though it never names the alternative explicitly.

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 explicit when-to-use or when-not-to-use guidance and no alternatives named, despite siblings like create_vse_strip and create_vse_transition that an agent could easily confuse with this one. The only hint is an implied use case (referencing another scene's camera or timeline).

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