capcut-mcp

Overview Schema Source Related Servers Discussions Admin

capcut_set_timeline

Adjust a CapCut draft's canvas size, frame rate, total duration, or SDR/HDR color space; duration changes don't trim clips and dry-run is default.

Instructions

Change canvas size, fps, total duration or colour space (SDR/HDR) of a draft. Duration cannot cut existing segments. Dry-run by default.

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": {
      "draft": "<draft>"
    },
    "name": "capcut_set_timeline"
  }
}

Input Schema

Name	Required	Description
`fps`	No
`draft`	Yes	Draft folder name inside the drafts root (from capcut_list_drafts).
`width`	No
`height`	No
`dry_run`	No	true (default): return the plan only. false: write to disk (CapCut must be closed).
`duration_s`	No
`color_space`	No	Project colour space (Configuración del proyecto > Espacio cromático)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: the safe dry-run default and the destructive limit on duration (it cannot shorten existing segments). However, it omits other mutation-relevant behavior such as the requirement that CapCut be closed for a write (only visible in the schema), and what happens to unspecified settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler; the operation and its target are front-loaded and the two caveats (duration limit, dry-run default) follow immediately.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the primary settings and the most important safety caveat, but leaves the write-safety precondition and side effects unexplained. It is adequate but not fully complete.

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?

Schema coverage is only 43%, so the description must compensate. It maps to most writable parameters (canvas size = width/height, fps, duration, colour space) and clarifies that duration means 'total duration' rather than a segment, but it says nothing about the required 'draft' parameter or the fps/duration value ranges beyond what the schema already covers.

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?

The description names a specific verb ('Change') plus the exact settings affected (canvas size, fps, total duration, colour space) on a named resource (a draft), so an agent can distinguish it from capcut_set_clip or capcut_set_speed_curve. It does not explicitly name a sibling it is differentiated from, which keeps it short of a 5.

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 alternatives such as capcut_create_draft or capcut_set_clip, nor any prerequisites (e.g. CapCut must be closed). The only usage-relevant statements are constraints ('Duration cannot cut existing segments') and the dry-run default, not routing information.

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