Skip to main content
Glama

Add Keyframe Animation

capcut_add_keyframe

Add keyframe-based property animations to video tracks using property types like scale, alpha, rotation, and position with interpolated values.

Instructions

Add keyframe-based property animation to tracks.

This tool creates smooth animations by interpolating between keyframe values.

Args:

  • draft_id (string): The draft ID

  • track_name (string): Name of track to animate

  • property_types (string[]): Properties to animate (scale_x, scale_y, alpha, rotation, position_x, position_y)

  • times (number[]): Keyframe times in seconds (at least 2)

  • values (string[]): Values for each keyframe (same length as times)

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

Examples:

  • Fade in: property_types=["alpha"], times=[0, 2], values=["0.0", "1.0"]

  • Zoom in: property_types=["scale_x", "scale_y"], times=[0, 2], values=["0.5", "1.5"]

  • Rotate: property_types=["rotation"], times=[0, 3], values=["0", "360"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add keyframes to
track_nameYesName of the track to animate
property_typesYesProperties to animate (e.g., scale_x, scale_y, alpha, rotation)
timesYesKeyframe times in seconds
valuesYesValues for each keyframe
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations are minimal (no readOnly or destructive hints), and the description adds that it creates animations but does not disclose behaviors like whether existing keyframes are overwritten or if operations are reversible.

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

Conciseness4/5

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

The description is well-structured with a summary, explanation, argument list, and examples. However, the argument list partially repeats schema details.

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?

Missing output schema and no description of return values. Also lacks information on prerequisites (e.g., draft must exist) and error handling, which would be helpful for such a tool.

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%, and the description adds value with examples that demonstrate how to combine properties, times, and values for effects like fade-in, zoom, and rotation.

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 keyframe-based property animation to tracks' with an explanation of interpolation. This distinguishes it from sibling tools that add audio, effects, etc.

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 or when not to use this tool, but the examples and context make it clear it's for animation. No exclusions or alternatives are mentioned.

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