Skip to main content
Glama

Create CapCut Draft

capcut_create_draft

Create a new video editing draft by setting width, height, and frame rate. Use this draft as a canvas to add media, text, and effects.

Instructions

Create a new video editing draft with specified dimensions and frame rate.

This tool initializes a new draft project that can be edited by adding videos, audio, text, images, and effects.

Args:

  • width (number): Video width in pixels (360-4096, default: 1920)

  • height (number): Video height in pixels (360-4096, default: 1080)

  • fps (number): Frames per second (24-120, default: 30)

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

Returns: { "draft_id": string, // Unique draft identifier for subsequent operations "width": number, // Video width "height": number, // Video height "fps": number, // Frame rate "duration": number, // Current duration (starts at 0) "created_at": string // ISO timestamp }

Examples:

  • Create HD draft: params with width=1920, height=1080

  • Create vertical video: params with width=1080, height=1920

  • Create 4K draft: params with width=3840, height=2160

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNoVideo width in pixels
heightNoVideo height in pixels
fpsNoFrames per second
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 indicate this is not readOnly or destructive, consistent with creating a new draft. The description adds that it initializes a project, but does not disclose that multiple calls create multiple independent drafts (non-idempotent).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with Args, Returns, and Examples, but it repeats schema information. Could be more concise by omitting redundant defaults.

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 no output schema, the description provides a detailed return example. Sibling tools are clearly different, and the description covers the essential behavior of creating a draft.

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 coverage is 100% with full parameter descriptions. The description mostly repeats schema info, but the Examples section adds practical context for choosing width/height combinations.

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 ('Create') and clearly identifies the resource ('video editing draft'). It distinguishes itself from sibling tools (which add elements) by focusing on creating the draft itself.

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 implies this is for starting a new project, but does not explicitly state when not to use it (e.g., if a draft already exists). The return of a draft_id provides implicit guidance.

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