Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

reorder_vse_strips

Reorder VSE strips by moving, swapping, closing gaps, or snapping them to adjacent boundaries or frames to organize timeline edits.

Instructions

Perform editorial reorganization on VSE strips: MOVE channel/position, SWAP channels between strips, CLOSE_GAPS between sequential strips on a channel, or SNAP to adjacent strip boundaries.

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": "reorder_vse_strips"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTarget strip name for MOVE or SNAP.
actionYesEditorial action to perform.
channelNoTarget channel for MOVE, or channel index for CLOSE_GAPS.
snap_toNoSnap alignment target.PREVIOUS_STRIP
strip_aNoFirst strip name for SWAP.
strip_bNoSecond strip name for SWAP.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
target_frameNoTarget timeline start frame for MOVE, or snap frame target for SNAP with snap_to='FRAME'.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose whether these editorial reorganizations are destructive or reversible, what permissions or approval workflow apply, or how task_id, request_id, and approval_token affect behavior. For a mutation tool with zero annotation coverage, substantial behavioral gaps remain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler, and each clause names one supported action and its relevant target. It communicates the action set efficiently without burying the core purpose.

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?

Purpose and action names are clear, but for an 11-parameter mutation tool with no annotations and no output schema, the description omits critical operational context: side effects, approval requirements, action-specific required fields, and error behavior. An agent would need to inspect the schema closely and still lack behavioral guidance.

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?

The description maps actions to key parameters: MOVE uses channel/position, SWAP uses channels between strips, CLOSE_GAPS uses sequential strips on a channel, and SNAP uses boundaries. However, it does not explain strip_a/strip_b pairing, target_frame semantics beyond 'position', or the purpose of the approval/request/task identifiers, and schema coverage is 73%.

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 and resource: 'editorial reorganization on VSE strips', then enumerates four discrete actions (MOVE, SWAP, CLOSE_GAPS, SNAP). An agent can distinguish this from creation, trimming, and transformation siblings by the reorder actions, though no sibling is explicitly named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action list implies when each operation applies, but there is no explicit guidance on choosing this tool over modify_vse_strip, transform_vse_strip, or trim_vse_strip, and no prerequisites or when-not conditions are given. Selection must be inferred from action names alone.

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