Skip to main content
Glama

Add Audio to Draft

capcut_add_audio

Add background music or sound effects to a CapCut draft, with adjustable volume and fade in/out effects.

Instructions

Add audio track to draft with volume and fade effects.

This tool adds background music or sound effects to the video timeline.

Args:

  • draft_id (string): The draft ID

  • audio_url (string): URL to audio file (mp3, wav, aac, m4a, flac, ogg)

  • start (number): Start time in seconds

  • end (number): End time in seconds

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

  • fade_in (number): Fade in duration in seconds (default: 0)

  • fade_out (number): Fade out duration in seconds (default: 0)

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

Examples:

  • Add background music: audio_url="https://...", volume=0.5

  • Add with fade: fade_in=2, fade_out=2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add audio to
audio_urlYesURL to the media file
startYesStart time in seconds
endYesEnd time in seconds
volumeNoAudio volume (0.0 to 1.0)
fade_inNoFade in duration in seconds
fade_outNoFade out duration in seconds
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations indicate mutating (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the accepted audio formats (mp3, wav, etc.) but does not disclose whether audio is appended or replaces existing tracks, or any limits.

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 structured with a summary sentence and an Args section. While the Args replicates schema info, it is clear and the examples are helpful. Could be slightly more concise.

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?

The tool has 8 parameters and no output schema. The description covers all parameters with examples, explaining start/end times and volume/fade. It does not explain return values, but for a simple addition tool this is acceptable.

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?

Schema coverage is 100%, baseline 3. The description enhances parameters by listing audio formats (mp3, wav, aac, m4a, flac, ogg) for audio_url and provides examples showing volume and fade usage, adding value beyond the schema.

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 an audio track to a draft, with volume and fade effects. It distinguishes from sibling tools like capcut_add_video (adds video) and capcut_add_effect (adds effects).

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?

No explicit guidance on when to use this tool vs alternatives. The description implies it is for adding audio (background music or sound effects), but does not compare to other add tools or specify prerequisites.

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