Loading ToolBench
MCP server for CapCut video editing automation, providing tools to create projects, manage clips, add text, and manipulate video properties
CapCut MCP has 15 tools with consistent naming (verb_noun pattern) and basic schemas. However, critical gaps undermine production readiness: (1) Output schemas are completely undocumented, no tool declares what fields it returns, forcing LLMs to guess downstream structure; (2) Parameter descriptions are minimal (10-30 chars), lacking constraints, ranges, or format guidance; (3) No error handling guidance, tools return bare error strings without recovery hints; (4) No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels; (5) Tool definitions are inferred from file structure rather than explicitly visible in registration code. Naming is strong (list_projects, get_project, add_text are clear), but descriptions lack the 50-200 char LLM-optimized range and omit dependency hints.
Adds a video or audio clip to a CapCut project
Adds a text segment to a CapCut project timeline
Creates a new CapCut project with specified parameters
Retrieves detailed information about a specific CapCut project
Retrieves timeline and track information for a CapCut project
Lists all available CapCut projects
Moves a clip to a different position on the timeline
Reads and returns the raw draft_content.json for a project
No output schemas documented. Tools return unstructured strings or JSON without declaring field names, types, or structure. LLMs cannot plan downstream calls or extract data reliably.
Parameter descriptions are too brief (10-30 chars) and lack constraints. E.g., 'volume' and 'opacity' accept 0.0 - 1.0 but description does not state range. 'blend_mode' accepts string but no enum or valid values listed.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
Removes a clip from a CapCut project timeline
Sets the blend mode of a clip
Sets whether a clip should loop
Sets the opacity/alpha of a clip
Sets transform properties (scale, rotation) of a clip
Sets the volume level of a clip
Trims a clip to a specified duration
No error handling guidance. Tools return bare error strings (e.g., 'Project not found: xyz') without recovery hints. LLMs cannot determine if error is retryable or what to do next.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked with Risk levels (READ_ONLY, WRITE, DESTRUCTIVE) in metadata but not exposed in MCP tool definitions, so clients cannot enforce safety policies.
Tool definitions inferred from file structure; explicit registration code not visible. Cannot verify tool names, descriptions, and schemas are correctly registered in MCP protocol.