Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

split_vse_strip

Split a video sequence strip at a specified frame into two contiguous strips on the same channel while preserving properties across the cut.

Instructions

Split a strip at a designated cut frame into two contiguous strips on the same channel, preserving properties across the cut.

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": {
      "name": "<name>",
      "split_frame": "<split_frame>"
    },
    "name": "split_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the strip to split.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
split_frameYesTimeline frame index where the split cut occurs (must be strictly between in-point and out-point).
approval_tokenNo
right_strip_nameNoOptional name for the new second (right) strip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose meaningful behavior: the strip becomes two contiguous strips, they stay on the same channel, and properties are preserved across the cut. It does not disclose what happens to the original strip's identity or name, whether the operation is undoable, or that an approval token/flow may be required, which the schema hints at via 'approval_token' and the untrusted 'approved' flag.

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 no filler; the verb and result come first. It is lean, though the brevity is partly why other dimensions are under-covered rather than the wording itself being 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?

For a seven-parameter mutation tool with no annotations and no output schema, one sentence is insufficient: the agent is not told what the call returns (the two strips? their identifiers?), how naming defaults work, or how the approval parameters interact. The security-relevant 'approved'/'approval_token' pair in particular gets no narrative treatment.

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?

At 57% schema coverage, the description adds only marginal meaning: "designated cut frame" maps to split_frame and "preserving properties" loosely implies how the new right strip inherits settings. It says nothing about the distinction between 'name' and 'right_strip_name', nor about 'task_id', 'request_id', 'approval_token', or the deprecated 'approved' flag.

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 gives a specific verb and resource ("Split a strip") plus the outcome ("into two contiguous strips on the same channel"). It is unambiguous about what the operation produces, but it never distinguishes itself from the closest sibling, trim_vse_strip, which an agent could plausibly pick instead.

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 when-to-use guidance at all: no statement about when splitting is preferable to trimming, no prerequisite about the strip being selected or active, and no mention of when the split is invalid beyond the schema's parenthetical about frame range. The agent must infer the context of use entirely.

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