capcut-mcp

Overview Schema Source Related Servers Discussions Admin

capcut_add_sticker

Add a sticker to a CapCut draft's sticker track using a cached resource ID, with position, scale, and rotation; dry-run previews changes before writing.

Instructions

Add a CapCut sticker on a sticker track by resource_id (sticker_id), with position/scale/rotation. The sticker must have been added once in CapCut so it is in Cache/artistEffect. Animate it with capcut_add_animation. 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>",
      "resource_id": "<resource_id>",
      "start_s": "<start_s>"
    },
    "name": "capcut_add_sticker"
  }
}

Input Schema

Name	Required	Description	Default
`x`	No
`y`	No
`name`	No
`draft`	Yes	Draft folder name inside the drafts root (from capcut_list_drafts).
`scale`	No
`track`	No		stickers
`dry_run`	No	true (default): return the plan only. false: write to disk (CapCut must be closed).
`start_s`	Yes
`rotation`	No
`duration_s`	No
`resource_id`	Yes	CapCut resource_id (digits), from docs/capcut_features.json or a CapCut-saved draft.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4/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 behavioral burden. It usefully discloses that the tool is dry-run by default and that the sticker must already exist in CapCut's cache, but it omits permission requirements, reversibility, failure modes, and the fact (buried in the schema) that writing requires CapCut to be closed.

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?

Three sentences, front-loaded with the core action before the prerequisite and the dry-run note. No filler, no repetition of the title, and each sentence adds a distinct fact.

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 an 11-parameter write tool with no annotations and no output schema, the description covers the decisive workflow facts (resource prerequisite, track, dry-run default, animation handoff). It is still thin on the remaining parameters and on what a dry-run versus real write returns, but the critical gaps are addressed.

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 27%, so the description must compensate. It clarifies the resource_id alias ('sticker_id'), the sticker track, and the position/scale/rotation group, but leaves name, duration_s, start_s, x/y, and track defaults unexplained beyond the schema itself.

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 ('Add a CapCut sticker on a sticker track by resource_id'), plus the key attribute group (position/scale/rotation). It also distinguishes itself from the animation sibling by routing that concern to capcut_add_animation, so an agent can separate this from capcut_add_effect/capcut_add_animation without opening a 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 a concrete precondition ('must have been added once in CapCut so it is in Cache/artistEffect') and names the follow-up tool for animation. It stops short of explicit when-not-to-use guidance or a direct contrast with the other 'add_*' siblings, so it is strong but not complete routing.

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