Loading ToolBench
MCP server for Shotcut video editor providing tools for project editing, rendering, media analysis, and video processing
Shotcut MCP has 30 well-named tools with consistent verb_noun patterns (create_project, edit_project, render_preview). All tools have descriptions (avg ~80 chars, within baseline 34 - 392). Input schemas are present and mostly complete with type definitions and required/optional fields. However, output schemas are NOT documented, critical gap for LLM planning. Parameter descriptions are sparse (many lack detail on format/constraints). Error handling is minimal; no recovery guidance or actionable error messages visible. Security: no evidence of secret injection or permission gates. Composition is strong, tools chain well (e.g., inspect_project → edit_project → render_preview). STDIO transport caps protocol readiness at 50.
Analyze media file for quality issues (silence, black frames, interlacing, loudness)
Cancel an active render job
Run comprehensive compatibility diagnostics for Shotcut/MLT runtime
Create a new Shotcut project with specified video profile and settings
Describe an MLT service's properties, parameters, and usage
Describe a system service and its capabilities
Detect available hardware video encoders on the system
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., what does inspect_project return? What fields enable edit_project?). Critical for tool chaining.
Parameter descriptions lack format/constraint details. E.g., 'fps_num' and 'fps_den' lack explanation of valid ranges or typical values (24, 30, 60?). 'mode' enum values documented in operation catalog but not in tool params. LLMs cannot validate inputs without explicit constraints.
No error handling guidance. Tools return errors but no recovery hints (e.g., 'media not found, try diagnose_missing_media'). Agents cannot self-correct or plan fallbacks.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2025-06-18+ | v2 |
Diagnose color workflow issues (SDR/HDR, colorspace, processing mode)
Analyze missing media in a project and suggest relinking strategies
Commit a batch of edit operations to a Shotcut project with validation and conflict detection
Expand a file path with environment variables and user home directory
Export project markers as chapter metadata for video files
Load and inspect a Shotcut project, returning structure, tracks, clips, and metadata
List available project backups
List available MLT services (producers, filters, transitions, generators)
List all active and recent render jobs
List available system services and their status
Open a project or media file in the Shotcut GUI application
Plan and preview a batch of edit operations without committing, showing the diff and validation results
Render a contact sheet grid of sampled frames from a project
Render a single frame preview of a project at a specified position
Render multiple frame previews from a project in batch
Query the status of a durable render job
Restore a project from a backup
Describe edit operation schemas and runtime contracts for project editing
Diagnose Shotcut/MLT runtime compatibility and configuration
Query Shotcut and MLT runtime status
Start a durable render job to export a project with specified preset and range
Get a summary of media file properties and metadata
Validate a Shotcut project for readiness, checking media availability and MLT service dependencies
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without parsing descriptions. Critical for safety.
STDIO transport only. Not remotely accessible; cannot be used by hosted MCP clients. Limits deployment to local/containerized environments.