Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

group_vse_meta_strip

Group VSE strips into a nested MetaStrip, ungroup one back into individual strips, or inspect its child strips to organize complex timeline edits.

Instructions

Group multiple strips into a nested MetaStrip container, ungroup an existing MetaStrip back into individual strips, or inspect internal nested strips in the 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": "group_vse_meta_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the meta strip (required for UNGROUP and INSPECT; optional for CREATE).
actionYesAction to perform: 'CREATE' (group strips into meta), 'UNGROUP' (separate meta strip), 'INSPECT' (query child strips).
channelNoTimeline channel index for the meta strip container (1 to 128).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
strip_namesNoList of strip names to group into the meta strip (required when action='CREATE').
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 behavioral burden, and it says nothing about what UNGROUP does to the container or child strips, whether the operation is reversible, what happens on name collisions, or the meaning of the approval/task/request fields. The presence of a DEPRECATED 'approved' flag and an 'approval_token' hints at a consent flow that the description never explains. For a structural mutation tool with zero annotation coverage this is a substantial gap.

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 that packs all three modes without filler. It is somewhat run-on and could be scannable as a short list, but no sentence 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 three-mode mutation tool with no annotations, no output schema, and five undocumented parameters, the definition leaves too much to inference. The description never explains return values or what INSPECT yields, and it does not address the consent/async fields, so an agent cannot confidently construct a CREATE or UNGROUP call from it alone.

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 adds conditional requirements for name and strip_names, but these are largely restated in the schema's own parameter descriptions, and the schema coverage is a middling 63%. Five parameters (channel, task_id, request_id, approved, approval_token) are given no meaning at all in the description, including the ambiguous async/consent fields that most need explanation.

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 resource (VSE strips / MetaStrip container) and three concrete operations: group into nested MetaStrip, ungroup back to individual strips, and inspect internal nested strips. An agent can tell this is the MetaStrip-structural tool rather than a generic strip editor like modify_vse_strip. It stops short of explicitly contrasting itself with any named sibling, so 4 rather than 5.

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 three action modes are spelled out, which implicitly tells the agent which mode maps to which intent, but the same mapping is already in the action enum description. There is no guidance on prerequisites, ordering (e.g. must a MetaStrip already exist to UNGROUP?), or when to prefer this over splitting/trimming siblings. Usage is inferable but not directed.

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