Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

trim_vse_strip

Trim a Video Sequence Editor strip's in-point and out-point handles, optionally rippling later strips on the same channel to keep timing aligned.

Instructions

Trim head (in-point) and/or tail (out-point) handles of a strip in the Video Sequence Editor (VSE), with optional ripple editing to shift subsequent strips on the same channel.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the strip to trim.
rippleNoWhether to ripple shift subsequent strips on the same channel by the duration delta.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
trim_modeNoTrim mode: ABSOLUTE frame position or RELATIVE frame delta.ABSOLUTE
request_idNo
left_handleNoNew left handle (in-point) frame or relative delta.
right_handleNoNew right handle (out-point) frame or relative delta.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully explains that ripple editing shifts subsequent strips on the same channel by the duration delta, but does not cover permissions, reversibility, error behavior, or how approval-related parameters affect execution.

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 description is a single, front-loaded sentence with no wasted wording. It states the core action first and adds the ripple behavior as a compact qualifier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with nine parameters, no annotations, and no output schema, so the description should do more than define the core action. It covers trimming and ripple semantics but omits approval/workflow context and practical constraints needed to invoke the tool safely.

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 67%, so the schema already documents several parameters. The description adds meaning for ripple behavior and head/tail handle semantics, but does not explain trim_mode ABSOLUTE vs RELATIVE, or clarify the roles of task_id, request_id, approval_token, and approved.

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 uses a specific verb and resource: trimming head/tail handles of a strip in the Video Sequence Editor. It also mentions optional ripple editing, which distinguishes the operation from split/crop siblings behaviorally. However, it does not explicitly name or contrast with those sibling tools.

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 description implies when to use the tool by saying it trims in/out points, but gives no explicit guidance on choosing it over split_vse_strip, crop_vse_strip, or modify_vse_strip. There are no stated preconditions, exclusions, or when-not-to-use cases.

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