Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_vse_strip_modifiers

Add, remove, update, or list color grading and strip modifiers such as color balance, curves, and masks on Video Sequence Editor strips.

Instructions

Add, remove, update, or list visual color grading and strip modifiers (COLOR_BALANCE, BRIGHT_CONTRAST, WHITE_BALANCE, TONEMAP, CURVES, HUE_CORRECT, MASK) on 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": {
      "action": "<action>",
      "name": "<name>"
    },
    "name": "manage_vse_strip_modifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
gainNoHighlights gain RGB [r, g, b] for COLOR_BALANCE.
liftNoShadows lift RGB [r, g, b] for COLOR_BALANCE.
muteNoMute modifier effect.
nameYesName of the target strip in the sequence editor.
gammaNoMidtones gamma RGB [r, g, b] for COLOR_BALANCE.
powerNoASC-CDL power RGB [r, g, b] for COLOR_BALANCE.
slopeNoASC-CDL slope RGB [r, g, b] for COLOR_BALANCE.
actionYesAction to perform on strip modifiers.
brightNoBrightness adjustment for BRIGHT_CONTRAST.
enableNoEnable or disable modifier in viewport/rendering.
offsetNoASC-CDL offset RGB [r, g, b] for COLOR_BALANCE.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
contrastNoContrast adjustment for BRIGHT_CONTRAST.
mask_timeNoTime mapping method for the mask.
request_idNo
tonemap_keyNoKey value for TONEMAP.
white_valueNoWhite point balance RGB [r, g, b] for WHITE_BALANCE.
tonemap_typeNoTonemapping algorithm for TONEMAP.
modifier_nameNoName of modifier (optional for ADD/LIST, required for REMOVE/UPDATE).
modifier_typeNoModifier type (required for ADD).
approval_tokenNo
color_multiplyNoOverall color balance multiplier.
input_mask_typeNoMasking input type.
input_mask_stripNoName of strip to use as a mask.
correction_methodNoColor correction formula for COLOR_BALANCE modifier.
tonemap_intensityNoIntensity for TONEMAP.

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 disclosure burden, yet it only says what the tool does. It never states whether changes are destructive or reversible, whether modifiers affect viewport only or the final render, what happens when a named modifier does not exist, or how the deprecated 'approved' flag and the task_id/request_id/approval_token fields interact with execution.

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 the verbs and resource up front and no filler. Listing all seven modifier types duplicates the schema enum, which is mild waste for a one-line description.

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 27-parameter, four-action tool with no output schema and no annotations, so the description should at minimum explain that the applicable parameters depend on the chosen action. It instead covers purpose only, leaving the action-to-parameter mapping to be inferred entirely from 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 89%, so each of the 27 parameters is already documented in the schema, and the baseline of 3 applies. The description adds no meaning beyond the enum values it repeats; it does not explain which parameters pair with which action.

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 concrete verbs (add, remove, update, list), the exact resource (strip modifiers on VSE strips), and enumerates the seven modifier types. 'Visual color grading' implicitly separates it from the sibling manage_vse_sound_modifiers, though that routing is never made explicit.

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?

No when-to-use guidance is given: nothing says when to pick this over modify_vse_strip, inspect_modifiers, or manage_vse_sound_modifiers. Prerequisites (a strip must already exist, which modifier types suit which task) and exclusions are entirely absent.

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