Skip to main content
Glama

Add Image to Draft

capcut_add_image

Add image overlays to videos with configurable position, scale, rotation, and animation effects.

Instructions

Add image overlay to video with positioning, scaling, rotation, and animation.

This tool adds static or animated images to the video timeline.

Args:

  • draft_id (string): The draft ID

  • image_url (string): URL to image file (jpg, jpeg, png, gif, webp, bmp)

  • start (number): Start time in seconds

  • end (number): End time in seconds

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

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

  • scale (number): Scale multiplier 0.1-5.0 (default: 1.0)

  • rotation (number): Rotation angle 0-360 degrees (default: 0)

  • animation (string): Animation effect (optional)

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

Examples:

  • Add logo: image_url="https://...", position_x=0.9, position_y=0.1, scale=0.3

  • Add rotating image: rotation=45, animation="zoom_in"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add image to
image_urlYesURL to the media file
startYesStart time in seconds
endYesEnd time in seconds
position_xNoHorizontal position (0.0 to 1.0)
position_yNoVertical position (0.0 to 1.0)
scaleNoScale multiplier
rotationNoRotation angle in degrees
animationNoAnimation effect to apply
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 non-readonly, non-destructive, non-idempotent, open-world. The description adds context about adding overlay to the timeline, which is helpful. No contradictions with annotations. It does not detail return values or error handling, but annotations already cover behavioral hints.

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 concise and well-structured with an Args section listing parameters clearly. Examples are included without unnecessary verbosity. Every sentence adds value.

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 tool has 10 parameters (4 required) and no output schema, the description adequately explains how to use the tool with examples. It does not describe the output format or return values, but the response_format parameter covers that. Missing some situational context (e.g., prerequisites like draft existence).

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%, so baseline is 3. The description adds value by providing default values, ranges (e.g., 0.1-5.0 for scale), and examples for parameters like position_x and rotation. This goes beyond 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 the tool adds an image overlay to video with positioning, scaling, rotation, and animation. It distinguishes itself from sibling tools (e.g., add_audio, add_video) by specifying the media type (image) and its capabilities.

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 provides examples and explains the tool's functionality, but it does not explicitly state when to use this tool over alternatives. Sibling names imply different media types, so usage context is somewhat clear, but lacking explicit 'when not to use' 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