Skip to main content
Glama

Add Text to Draft

capcut_add_text

Overlay styled text on videos with customizable fonts, colors, shadows, and animations for titles and subtitles.

Instructions

Add styled text overlay to video with positioning, colors, shadows, and animations.

This tool creates text elements with full styling control including fonts, colors, backgrounds, shadows, and animations.

Args:

  • draft_id (string): The draft ID

  • text (string): Text content to display (1-500 characters)

  • start (number): Start time in seconds

  • end (number): End time in seconds

  • font (string): Font family name (optional)

  • font_size (number): Font size 12-200 (default: 48)

  • font_color (string): Hex color e.g., #FFFFFF (default: #FFFFFF)

  • background_color (string): Background hex color (optional)

  • background_alpha (number): Background opacity 0.0-1.0 (default: 0.8)

  • shadow_enabled (boolean): Enable shadow (default: false)

  • shadow_color (string): Shadow hex color (default: #000000)

  • position_x (number): Horizontal position 0.0-1.0 (default: 0.5 center)

  • position_y (number): Vertical position 0.0-1.0 (default: 0.5 center)

  • animation (string): Animation effect (fade_in, slide_up, slide_down, slide_left, slide_right, zoom_in, bounce)

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

Examples:

  • Add title: text="Welcome", font_size=72, position_y=0.2, animation="fade_in"

  • Add subtitle: text="Subscribe!", font_size=36, background_color="#000000"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add text to
textYesThe text content to display
startYesStart time in seconds
endYesEnd time in seconds
fontNoFont family name
font_sizeNoFont size in points
font_colorNoFont color in hex format#FFFFFF
background_colorNoBackground color in hex format
background_alphaNoBackground opacity (0.0 to 1.0)
shadow_enabledNoEnable text shadow
shadow_colorNoShadow color in hex format#000000
position_xNoHorizontal position (0.0 to 1.0, where 0.5 is center)
position_yNoVertical position (0.0 to 1.0, where 0.5 is center)
animationNoAnimation effect to apply
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

Annotations already indicate this is not read-only or destructive. The description adds that the tool 'creates text elements with full styling control', accurately reflecting its mutating behavior. No contradiction or missing behavioral traits.

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 well-structured: a concise summary sentence, a second sentence elaborating styling control, a detailed args list, and practical examples. No wasted words.

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 the complexity (15 parameters, no output schema), the description covers input thoroughly with schema and examples. However, it does not mention the return value (e.g., whether it returns a text element ID or success status), which is a gap for a tool without output schema.

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

Parameters5/5

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

Schema description coverage is 100%, but the description adds value by providing defaults, ranges, and examples for parameters (e.g., position_x/y default 0.5 = center, animation enum values). This exceeds what the schema provides.

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 'Add styled text overlay to video' with explicit mention of positioning, colors, shadows, and animations. It distinguishes from sibling tools (e.g., capcut_add_audio, capcut_add_video) by focusing on text overlay.

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 does not explicitly state when to use this tool vs alternatives, but the examples (e.g., adding title or subtitle) and the resource focus imply its appropriate context. It lacks explicit 'when not to use' or comparison to siblings.

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