Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_vse_transition

Creates a transition effect between two overlapping or adjacent Video Sequence Editor strips, supporting CROSS, WIPE, ALPHA, and COLORMIX types to blend clips.

Instructions

Create a transition effect (CROSS, GAMMA_CROSS, WIPE, ALPHA_OVER, ALPHA_UNDER, COLORMIX) between two overlapping or adjacent strips in the Video Sequence Editor (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": {
      "transition_type": "<transition_type>",
      "input1": "<input1>",
      "input2": "<input2>"
    },
    "name": "create_vse_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the transition strip. Auto-generated if omitted.
angleNoWipe angle in radians.
input1YesName of the first (outgoing / lower) input strip.
input2YesName of the second (incoming / upper) input strip.
channelNoChannel index for the transition strip.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationNoTransition duration in frames (defaults to overlap length).
directionNoWipe direction (IN or OUT).OUT
wipe_typeNoWipe transition pattern type for WIPE transitions.SINGLE
blur_widthNoWipe edge blur factor (0.0 to 1.0).
request_idNo
frame_startNoTimeline start frame (defaults to overlap start).
approval_tokenNo
transition_typeYesType of transition to create.

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?

With no annotations, the description carries the full behavioral burden. It discloses only the geometric precondition (overlapping/adjacent strips) and says nothing about whether this mutates or creates a strip on the timeline, what happens if the strips do not overlap, whether channel/frame_start are auto-resolved, permissions required, or whether the operation is idempotent.

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?

One compact sentence with the key enumeration front-loaded and no filler. It could have used a second short sentence for the overlap/channel behavior, but nothing present is wasteful.

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?

This is a 15-parameter mutation tool with no annotations and no output schema, so the description should explain the overlap requirement, default resolution for duration/frame_start/channel, and the effect on existing strips. It covers only the transition type list and the strip relationship, leaving the agent under-informed for a complex creation call.

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 80%, so the schema already documents nearly all parameters including enums for transition_type, wipe_type and direction. The description adds only the enumeration of transition types and the input-strip relationship, which is consistent with the baseline 3 when the schema does the heavy lifting.

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+resource ('Create a transition effect') and enumerates the exact transition types, scoping it to the Video Sequence Editor. It does not explicitly contrast with siblings like configure_vse_effect or create_vse_strip, but the 'between two strips' framing makes the resource distinct enough to select correctly.

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?

The phrase 'between two overlapping or adjacent strips' implies a precondition, but there is no explicit when-to-use guidance, no statement of when not to use it, and no routing to alternatives such as configure_vse_effect. An agent must infer the entire usage decision from the name and schema.

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