Skip to main content
Glama
Sign In
Arkeonix CapCut MCP

Arkeonix CapCut MCP

by daviilpzDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capcut_align_linked_segments

Aligns audio, image, and subtitle segments in the current sequence, using each audio's duration to determine segment timing.

Instructions

Align audio, image and subtitle segments by current order, using each audio duration.

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_align_linked_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
textTrackIndexNo
videoTrackIndexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Align' and does not disclose whether positions are moved destructively, whether audio durations are modified, whether the operation is reversible, or how linked groups are affected.

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?

The description is a single efficient sentence with no wasted words. The action and resources are front-loaded, though the brevity leaves important context unaddressed.

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 tool with three parameters, no annotations, and no output schema, the description omits essential invocation details: what draft is, how segments are selected, and how track indices affect behavior. It conveys the core operation but is not sufficient to call the tool correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain 'draft', 'textTrackIndex', or 'videoTrackIndex'. An agent cannot determine what the required draft refers to or how optional track indices scope the alignment.

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?

The description states a specific action ('Align') and explicit segment types ('audio, image and subtitle segments'), plus the alignment rule ('by current order, using each audio duration'). This distinguishes it clearly from sibling operations such as move_segment, trim_segment, or set_props, even without naming alternatives.

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, what prerequisite state is required, or whether it operates on selected/linked segments or whole tracks. The description implies a use case but does not state it.

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