Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_vse_effect

Creates, updates, or inspects visual effect strips in Blender's Video Sequence Editor, including blur, glow, speed, adjustment, and color-mix effects.

Instructions

Create, update, or inspect visual effect strips (GAUSSIAN_BLUR, GLOW, SPEED, ADJUSTMENT, COLORMIX) 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": {
      "action": "<action>"
    },
    "name": "configure_vse_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteNoMute state of the effect strip.
nameNoName of the effect strip (required for UPDATE and INSPECT, optional for CREATE).
clampNoMaximum luminance clamp for GLOW.
actionYesEffect action: CREATE new effect strip, UPDATE existing effect properties, or INSPECT effect settings.
size_xNoHorizontal blur size for GAUSSIAN_BLUR.
size_yNoVertical blur size for GAUSSIAN_BLUR.
channelNoChannel index for the effect strip.
qualityNoGlow calculation quality (1 to 5).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationNoDuration in frames (defaults to input_strip.duration if provided).
thresholdNoLuminance threshold for GLOW.
request_idNo
blend_alphaNoEffect blend opacity (0.0 to 1.0).
blur_radiusNoGlow blur radius.
effect_typeNoType of visual effect strip (required for CREATE).
frame_startNoTimeline start frame (defaults to input_strip.left_handle if provided).
input_stripNoSource strip name to apply effect to (required for GAUSSIAN_BLUR, GLOW, SPEED).
boost_factorNoGlow brightness multiplier.
speed_factorNoPlayback speed multiplier for SPEED effect.
speed_controlNoSpeed control method.MULTIPLY
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?

With no annotations present, the description carries the entire behavioral burden, yet it discloses nothing about mutation side effects, reversibility/undo, permission requirements, or what happens to the target strip. It also gives no hint that input_strip is mandatory for certain effect types, which is a meaningful behavioral constraint for an agent to know before invoking.

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 with zero filler that puts the resource and effect types first. It is efficient, though its brevity is also the source of the missing usage and behavioral detail rather than a virtue in itself.

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 22-parameter mutation tool with no annotations and no output schema, the definition is far too thin: it explains neither the create-vs-update lifecycle nor the conditional parameter requirements per effect type. An agent could still call it, but only by leaning entirely on the schema.

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 86%, so the schema already carries per-parameter meaning (e.g., size_x/size_y for GAUSSIAN_BLUR, clamp for GLOW, speed_factor for SPEED). The description only lists the effect type enum and adds no parameter-level guidance beyond that, so the baseline 3 is appropriate.

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 specific verbs (create, update, inspect) and a concrete resource (visual effect strips in the VSE), and it enumerates the five supported effect types, which clearly separates it from siblings like configure_vse_audio or configure_vse_text_style. It stops short of a 5 because it never explicitly contrasts itself with adjacent tools such as modify_vse_strip.

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 only usage signal is the trio of actions, which is already fully captured by the action enum in the schema. There is no statement of when to pick this tool over siblings, no prerequisites (e.g., needing an existing strip for UPDATE/INSPECT), and no exclusions.

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