Skip to main content
Glama
Sign In
Arkeonix CapCut MCP

Arkeonix CapCut MCP

by daviilpzDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capcut_auto_insert_broll

Insert B-roll cutaways onto an overlay track at specified timestamps in a CapCut draft. Provide video or image assets with start times and optional duration, scale, or animation to automate overlay edits.

Instructions

Automatically place B-Roll cutaways (videos/images) on an overlay track at designated timestamps.

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>",
      "insertions": "<insertions>"
    },
    "name": "capcut_auto_insert_broll"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
insertionsYeslist of B-Roll cutaways to insert
trackIndexNotarget B-Roll video track index (default: track 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must disclose mutation behavior. 'Place' implies modifying the timeline, but it does not explain side effects like whether the overlay track is created, whether existing B-Roll is replaced, permissions needed, or reversibility. This is a significant gap for a mutation tool without annotation support.

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?

The description is a single concise sentence that front-loads the main function with no filler. Every element ('B-Roll cutaways', 'overlay track', 'designated timestamps') contributes meaning, making it appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and an undocumented required draft parameter, the description is insufficient. An agent cannot infer prerequisites, side effects, or how to specify the draft target, making it incomplete for safe invocation.

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 67% (draft lacks a description). The description adds context for insertions (B-Roll cutaways, timestamps) and trackIndex (overlay track), but the draft parameter remains unexplained. It partially compensates for the schema gap but does not fully clarify all three parameters.

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 uses a specific verb ('place') and resource ('B-Roll cutaways on an overlay track at designated timestamps'), making the core function clear. It is distinguishable from siblings like capcut_add_video or capcut_add_image by emphasizing the automated overlay placement, though it does not explicitly name a differentiating sibling.

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?

The description gives clear context that this tool is for placing multiple B-Roll cutaways at specified timestamps, which implies batch/automated use. However, it does not explicitly state when NOT to use it or point to alternatives (e.g., capcut_add_video for single clips), leaving some inference to the agent.

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

Deploy Server

Other Tools