capcut-mcp

Overview Schema Source Related Servers Discussions Admin

capcut_add_text

Add a text overlay (title, hook, or CTA) to a CapCut draft with timing, duration, color, font size, and x/y placement; preview the plan before writing.

Instructions

Add a text overlay (title, hook, CTA) to a draft. Position x/y is -1..1 from the canvas centre. 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>",
      "text": "<text>",
      "start_s": "<start_s>",
      "duration_s": "<duration_s>"
    },
    "name": "capcut_add_text"
  }
}

Input Schema

Name	Required	Description	Default
`x`	No
`y`	No
`text`	Yes
`color`	No		#FFFFFF
`draft`	Yes	Draft folder name inside the drafts root (from capcut_list_drafts).
`track`	No		text
`dry_run`	No	true (default): return the plan only. false: write to disk (CapCut must be closed).
`start_s`	Yes
`font_size`	No
`duration_s`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden. It usefully discloses that writes are dry-run by default and defines the x/y coordinate space, which are real behavioral facts. However it omits that the write path requires CapCut to be closed and says nothing about what a dry-run plan returns.

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?

Three tight sentences with no filler, and the most important constraint (dry-run default) is placed prominently at the end of a short block. Slightly clipped, but every sentence earns its place.

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 10-parameter mutation tool with no annotations and no output schema, the description leaves several gaps: units for timing parameters, the CapCut-must-be-closed precondition, and any hint of what is returned. It is adequate but not complete for the tool's complexity.

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 description coverage is only 20% across 10 parameters, so the description must compensate. It adds meaning for x/y ('-1..1 from the canvas centre') and reinforces the dry_run default, but leaves start_s/duration_s units, color format, font_size, and track semantics to the raw 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+resource ('Add a text overlay ... to a draft') and gives concrete examples of the content type (title, hook, CTA). It is distinguishable from capcut_add_subtitles and capcut_style_text, though the description never names those siblings or clarifies the boundary.

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

Usage Guidelines3/5

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

Usage is implied (attach text overlays to a draft) and the dry-run default is called out, which is useful for knowing the safe path. But there is no explicit when-to-use versus when-not, no mention of prerequisites for real writes, and no routing to alternative text tools.

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