Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

crop_vse_strip

Set pixel crop boundaries (min_x, max_x, min_y, max_y) on a VSE strip to control visible framing, or inspect existing crop values.

Instructions

Configure pixel cropping boundaries (min_x, max_x, min_y, max_y) on a strip 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": {
      "name": "<name>"
    },
    "name": "crop_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target strip in the sequence editor.
max_xNoRight crop margin in pixels.
max_yNoTop crop margin in pixels.
min_xNoLeft crop margin in pixels.
min_yNoBottom crop margin in pixels.
actionNoAction: UPDATE crop properties or INSPECT current crop boundaries.UPDATE
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 behavioral burden. 'Configure' implies a mutation, but the description does not state that this modifies the strip, whether changes are reversible, that INSPECT is a read-only mode on the same tool, or anything about the approval_token/approved consent machinery the schema hints at.

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 tight sentence with the core action front-loaded and zero filler. It is efficient, though brevity here contributes to the missing guidance rather than compensating for it.

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 10-parameter mutation tool with no annotations and no output schema, the description is far too thin. The dual UPDATE/INSPECT behavior, the meaning of the crop bounds when only a subset is provided, and the trust/approval semantics of approved and approval_token all go unaddressed.

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 enumerates the four crop parameters, which the schema already documents individually, and adds no further meaning (units beyond pixels, behavior when only some bounds are set, or how bounds interact). It says nothing about action, task_id, request_id, or approval_token, leaving several of the 10 parameters unexplained in prose.

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 ('Configure') and resource ('pixel cropping boundaries ... on a strip in the VSE'), and names the four boundary parameters. The 'strip in the VSE' qualifier separates it from sibling image-cropping tools like crop_reference_image, though no sibling is explicitly named.

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 tool versus siblings such as crop_reference_image, trim_vse_strip, or transform_vse_strip. Critically, the description never mentions that the 'action' parameter supports both UPDATE and INSPECT modes, so an agent cannot tell from the text that this tool also reads existing crop values.

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