Skip to main content
Glama

add_image

Insert an image file into a CapCut video project as a still clip. Specify duration and timeline position, or append to the end.

Instructions

Add an image to the project's video track as a still clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute path to the image file.
duration_msNoHow long to show the image (ms). Default 5000 (5 seconds).
position_msNoWhere to place it on the timeline (ms). Use -1 to append.
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 provided, so description carries full burden. Only states basic action without disclosing behavior like error handling (e.g., missing file), overwrite behavior, or timeline effects.

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 that directly conveys the purpose without extraneous words. Front-loaded and efficient.

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

Completeness3/5

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

Adequate for a simple add operation, but lacks specification on file format support, error behavior, and interaction with existing clips. Output schema exists but unknown content.

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 baseline is 3. Description adds 'still clip' context but does not provide additional meaning beyond the schema's parameter descriptions.

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?

Clearly states the action 'Add' and the resource 'an image to the project's video track as a still clip'. This distinguishes it from sibling tools like add_video (adds video) and add_audio (adds audio).

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 vs. alternatives like add_media_batch. No prerequisites or limitations mentioned (e.g., supported image formats, project existence).

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