Skip to main content
Glama
Sign In
Arkeonix CapCut MCP

Arkeonix CapCut MCP

by daviilpzDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capcut_set_audio_fade

Set fade-in and fade-out durations on audio or video clips in CapCut drafts. Specify seconds to control transition timing and prevent abrupt audio cuts.

Instructions

Set fade-in and fade-out durations on an audio or video clip.

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>",
      "segmentId": "<segmentId>"
    },
    "name": "capcut_set_audio_fade"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
fadeInSecNofade-in duration in seconds (default: 0.0)
segmentIdYestarget audio/video segment ID
fadeOutSecNofade-out duration in seconds (default: 0.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description alone must disclose behavior. It states the mutation ('Set') but does not mention whether existing fades are replaced, whether changes are reversible, whether the draft must be saved, or what the tool returns.

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 front-loaded sentence with no filler. Every word contributes to understanding the tool's core purpose.

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?

This is a relatively simple tool and the schema covers most parameters, so the description plus schema is minimally sufficient for an agent to invoke it. Still, without annotations or an output schema, behavioral details and return expectations are left unstated.

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?

The schema already documents fadeInSec, fadeOutSec, and segmentId including defaults and target type. The description adds little beyond 'audio or video clip', and the required `draft` parameter remains undocumented in both the schema and the description.

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 uses a specific verb ('Set') with a clear resource ('fade-in and fade-out durations') and target ('audio or video clip'). This clearly distinguishes the tool from siblings like capcut_apply_audio_effect, capcut_normalize_audio, or capcut_set_props.

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?

The intended use is implied by the name and description: use this when the user wants to apply fade durations to a clip. However, there is no explicit guidance about when not to use it or which alternatives might be better for related audio adjustments.

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