Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

mixdown_vse_audio

Mix down all active audio strips from the Video Sequence Editor timeline and export them as a single audio file in WAV, FLAC, MP3, OGG, or AAC format.

Instructions

Mix down and export all active audio strips from the Video Sequence Editor timeline to a dedicated audio sound file (WAV, FLAC, MP3, OGG, AAC).

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": {
      "output_path": "<output_path>"
    },
    "name": "mixdown_vse_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
codecNoAudio codec (inferred from container if omitted).
formatNoAudio bit depth / sample format (default: S16).S16
bitrateNoAudio bitrate in kbps for compressed formats (default: 192).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
channelsNoChannel layout (default: STEREO).STEREO
containerNoAudio container format (inferred from output_path extension if omitted).
request_idNo
output_pathYesDestination file path for the mixed audio file (path traversal forbidden).
sample_rateNoAudio sample rate in Hz (default: 48000).
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/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. It does add real behavioral context that the schema cannot convey: the operation sweeps ALL active audio strips rather than a selection, and it writes a single self-contained file. It omits important traits for a file-writing operation, such as overwrite behavior for an existing output_path, filesystem permission requirements, and whether the timeline or source strips are modified.

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 the action, scope and output stated before the format parenthetical; there is no filler. It is efficient, though the format list partially duplicates the container enum and could carry one clarifying clause (e.g. overwrite or return value) at no length cost.

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?

For a simple export action the core is covered: what is mixed (all active audio strips), what is produced (a single audio file), and where it goes (output_path). Given 11 parameters, no annotations, and no output schema, the definition is thin on side effects, overwrite semantics, and what the call returns, which an agent needs before invoking a file-writing tool.

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 parenthetical format list (WAV, FLAC, MP3, OGG, AAC) maps onto the container enum and gives some meaning for that parameter family. But with 11 parameters at 73% schema coverage, the description says nothing about codec, bit depth, sample rate, channel layout, bitrate, or the approval_token/task_id/request_id fields, so it adds only marginal meaning beyond the schema.

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 ('Mix down and export all active audio strips from the Video Sequence Editor timeline') plus the output artifact, which is far more informative than the bare name. It implicitly separates itself from sequence rendering by being audio-only, but never names a sibling such as render_vse_sequence or configure_vse_audio to make the distinction explicit.

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 when-to-use or when-not-to-use guidance and no naming of alternatives. An agent must infer on its own whether mixdown is the right call versus render_vse_sequence or configure_vse_audio, and no prerequisites (e.g. an existing VSE timeline with audio strips) are stated.

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