Skip to main content
Glama

Add Video to Draft

capcut_add_video

Add a video clip to an existing draft with precise timing, volume control, transitions, and speed adjustments.

Instructions

Add a video clip to an existing draft with timing, volume, and effects.

This tool adds video content to the timeline with support for transitions, speed adjustments, and volume control.

Args:

  • draft_id (string): The draft ID from create_draft

  • video_url (string): URL to video file (mp4, mov, avi, mkv, webm, flv)

  • start (number): Start time in seconds (>= 0)

  • end (number): End time in seconds (> 0)

  • volume (number): Audio volume 0.0-1.0 (default: 1.0)

  • transition (string): Optional transition effect (fade_in, fade_out, dissolve, wipe, slide, zoom)

  • speed (number): Playback speed 0.1-10x (default: 1.0)

  • response_format ('markdown' | 'json'): Output format

Examples:

  • Add background video: draft_id="abc123", video_url="https://...", start=0, end=10

  • Add with slow motion: speed=0.5

  • Add with fade in: transition="fade_in"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add video to
video_urlYesURL to the media file
startYesStart time in seconds
endYesEnd time in seconds
volumeNoAudio volume (0.0 to 1.0)
transitionNoTransition effect to apply
speedNoPlayback speed multiplier
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds transparency by detailing supported video formats, parameter defaults, and typical modifications (adding to timeline). No contradictions with annotations.

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 well-structured with a summary paragraph, Args list, and Examples. It is front-loaded with the main purpose and avoids redundancy. Could be slightly shortened but is efficient.

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?

Given 8 parameters and no output schema, the description covers core functionality, required/optional params, and examples. However, it lacks details on error handling or prerequisites beyond draft_id. Still adequate for a clear use case.

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

Parameters4/5

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

Input schema has 100% coverage, but the description adds value by listing supported video formats (mp4, mov, etc.) not in schema, and provides practical examples that clarify parameter combinations. Defaults are also reiterated.

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 clearly states the tool adds a video clip to an existing draft with specific capabilities (timing, volume, effects). It distinguishes itself from siblings like capcut_add_audio by explicitly mentioning 'video clip' and provides a specific verb-resource pair.

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 description implies usage after creating a draft and provides examples, but lacks explicit guidance on when to use this tool vs alternatives like capcut_add_audio or capcut_add_image. No when-not-to-use conditions are stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eery1677-lab/capcut-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server