BCD — Bridge Control Delegate

video_edit

Destructive

Edit videos on this Mac into a new file: cut and join clips, change speed, reframe to vertical (9:16) or other shapes, add titles, captions or subtitles (burned in) and a logo, put music under it, fade and crossfade, or export audio only (.m4a) or a GIF. Clips play in order; each uses start/end seconds from its own file. texts and captions use times on the finished video. Output never overwrites an existing file unless overwrite is true. Runs in the background: it waits up to waitMs, then returns a jobId to poll with video_status. Use video_frames on the result to check it.

Input Schema

TableJSON Schema

Name	Required	Description
`clips`	Yes
`music`	No
`texts`	No	Titles and labels; default position top
`fadeIn`	No
`images`	No
`output`	Yes
`waitMs`	No
`fadeOut`	No
`captions`	No
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`crossfade`	No	Seconds of overlap between clips
`captionStyle`	No
`captionsFile`	No	.srt file to burn in as captions
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / workSessionId

Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare destructiveHint=true, and the description adds meaningful context beyond them: output never overwrites an existing file unless overwrite is true, the call is asynchronous with a waitMs/ jobId polling model, and clip times vs. finished-video times are separated. That is substantial behavioral disclosure for a mutation tool.

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?

Front-loads the capability list and then layers the timing and async semantics; nearly every sentence carries information. It is dense and list-like rather than tautological, though the long feature enumeration could be tightened slightly.

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

Completeness4/5

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

For a 14-parameter, nested-object tool with no output schema and low schema coverage, it covers the highest-risk unknowns (async job model, overwrite safety, timing semantics, output file types). Gaps remain around output format parameters and device/work-session scoping, but the core call path is understandable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 36%, so the description must compensate, and it does for the hardest semantics: 'clips play in order; each uses start/end seconds from its own file' versus 'texts and captions use times on the finished video,' plus the overwrite flag. It leaves many parameters (fit, codec, resolution, gif settings, deviceId, workSessionId) unexplained, keeping it short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Edit videos on this Mac into a new file') and enumerates concrete operations: cut/join, speed, reframe to 9:16, titles/captions, music, fades, audio-only or GIF export. It explicitly routes to siblings video_status and video_frames, so an agent can place it among the video_* tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational context: runs in the background, waits up to waitMs, then returns a jobId to poll with video_status, and use video_frames on the result to verify. It does not explicitly contrast with video_info or video_transcribe, but the workflow guidance is concrete enough to call correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?