Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_vse_text_strip

Create a dedicated text or subtitle strip in Blender's Video Sequence Editor with typography, placement, alignment, shadow, outline, and background box styling.

Instructions

Create a dedicated text or subtitle strip in the Video Sequence Editor (VSE) with typography, placement, alignment, shadow, outline, and background box styling.

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": {
      "text": "<text>",
      "channel": "<channel>",
      "frame_start": "<frame_start>",
      "duration": "<duration>"
    },
    "name": "create_vse_text_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional unique name for the text strip.
textYesText content to display.
colorNoText color as RGBA [r, g, b, a].
channelYesTimeline channel index (1 to 128).
task_idNo
use_boxNoEnable background box behind text.
anchor_xNoHorizontal anchor alignment.
anchor_yNoVertical anchor alignment.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
durationYesDuration in frames.
locationNoNormalized screen coordinates [x, y] (0.0 to 1.0).
use_boldNoRender text in bold weight.
box_colorNoBackground box RGBA color [r, g, b, a].
font_sizeNoFont size in points.
box_marginNoBackground box padding margin.
request_idNo
use_italicNoRender text in italic slant.
use_shadowNoEnable drop shadow behind text.
wrap_widthNoWord wrap width (0.0 = no wrap).
alignment_xNoHorizontal text alignment.
frame_startYesTimeline start frame.
shadow_blurNoShadow edge blur radius.
use_outlineNoEnable text outline stroke.
shadow_colorNoShadow RGBA color [r, g, b, a].
box_roundnessNoBackground box corner roundness (0.0 to 1.0).
outline_colorNoOutline stroke RGBA color [r, g, b, a].
outline_widthNoOutline stroke width.
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?

With no annotations, the description carries the full behavioral burden. It says 'create' but does not disclose what happens on the timeline (channel occupancy, overlap with existing strips, minimum duration constraints), nor does it mention the approval-related arguments (approved, approval_token) or task_id/request_id, which materially affect whether a call will succeed.

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 well-formed sentence that is front-loaded with the action and target, with the styling scope appended. No filler or repetition, though the styling enumeration is slightly list-like rather than prioritized.

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 28-parameter mutation tool with no annotations and no output schema, the description leaves out critical operational context: how the strip is placed relative to existing strips, whether the call requires approval, and what a successful return looks like. The styling summary is accurate but covers only the cosmetic half of the tool's surface.

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 high at 89%, so the schema already explains nearly every parameter including enums for anchor_x/anchor_y/alignment_x. The description only groups the styling surface into categories (typography, placement, alignment, shadow, outline, box), adding framing but no per-parameter meaning beyond the schema — baseline 3.

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 ('Create a dedicated text or subtitle strip') plus the exact subsystem ('Video Sequence Editor (VSE)'), and enumerates the styling domains covered (typography, placement, alignment, shadow, outline, background box). It separates itself reasonably from generic siblings like create_text by naming the VSE and 'strip', but it does not explicitly contrast with create_vse_strip or configure_vse_text_style.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative despite several plausible siblings (create_text, create_vse_strip, configure_vse_text_style). The only implied guidance is that this is the choice when the text must live on the VSE timeline, which the agent must infer.

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