Skip to main content
Glama

add_text

Insert a text overlay into a CapCut project at a specific time, with options for duration, font, color, and alignment.

Instructions

Add a text overlay to the project at a specific time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNoText color as hex string (e.g., "#FFFFFF" for white, "#FF0000" for red).#FFFFFF
contentYesThe text content to display.
start_msNoWhen the text appears on the timeline (milliseconds).
alignmentNoText alignment — 0=left, 1=center, 2=right. Default 1 (center).
font_sizeNoFont size. Default 15.0.
duration_msNoHow long the text stays visible (ms). Default 3000 (3s).
project_nameYesName of the CapCut project.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It only mentions adding text at a specific time, lacking details about effects on the project, error handling, or return values.

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?

Single sentence with no wasted words. Verb first, clearly states action and target.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 7 parameters and an output schema, the description is minimal and does not explain key context like that it modifies a CapCut project, that it creates an overlay, or how it interacts with the timeline.

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%, so parameters are well-described in the schema. The description adds no additional meaning beyond 'at a specific time' which is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it adds a text overlay to the project at a specific time. It distinguishes from sibling tools like add_image and add_video, but does not differentiate from add_subtitles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like add_subtitles or update_text_content. No exclusions or context of usage provided.

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/baizo7/capcut_MCP_server-'

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