Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

delete_vse_strip

Removes and unlinks a named strip from Blender’s Video Sequence Editor, helping clean up or reorganize VSE timelines.

Instructions

Remove and unlink a strip from the Blender Video Sequence Editor (VSE) by name.

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>"
    },
    "name": "delete_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the strip to delete.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
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?

No annotations are supplied, so the description carries the full burden for a destructive operation, yet it never states whether deletion is permanent or undoable, what happens to linked audio or adjacent strips, or what is returned. The schema's approved/approval_token fields hint at a consent gate that the description never explains, leaving the actual safety behavior opaque.

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, stating the action, target, and key up front. It is perhaps too terse for a destructive tool, but nothing in it is wasted.

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 destructive five-parameter tool with no annotations and no output schema, the description is thin: it omits reversibility, side effects on linked strips, and the meaning of the approval-related arguments. An agent could invoke it, but not with confidence about consequences.

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 40% across five parameters, and the description only restates the 'name' key that the schema already documents. The four ancillary parameters (task_id, request_id, approved, approval_token) receive no explanation of their role in the deletion flow, so the description does not compensate for the coverage gap.

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 a specific verb pair ("Remove and unlink"), a concrete resource (a strip in the Blender Video Sequence Editor), and the lookup key ("by name"). It is immediately clear what the tool does, though it offers no differentiation from sibling deletion tools such as delete_object or delete_keyframe.

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 guidance on when to use this versus alternatives like trim_vse_strip, split_vse_strip, or delete_object, nor any stated preconditions. The only usage signal is the implied 'you have a strip name you want gone,' which the name alone already conveys.

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