Skip to main content
Glama

Add Sticker to Draft

capcut_add_sticker

Add decorative stickers or emojis to a video draft with custom positioning, scale, and rotation. Specify start and end times for timed overlays.

Instructions

Add sticker/emoji overlay with positioning and transformation.

This tool adds decorative stickers or emojis to the video.

Args:

  • draft_id (string): The draft ID

  • sticker_url (string): URL to sticker image

  • 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)

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

Examples:

  • Add corner sticker: position_x=0.9, position_y=0.1, scale=0.2

  • Add rotating emoji: rotation=15, scale=0.5

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add sticker to
sticker_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
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior2/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description does not add behavioral context beyond stating it 'adds decorative stickers or emojis'. No mention of side effects, authorization needs, or state changes.

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 front-loaded with a concise summary, followed by a clear Args list and relevant examples. Every sentence adds value without redundancy.

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?

The description covers parameter usage, defaults, and examples comprehensively. However, it does not describe the return value or response structure, which would be useful given no output schema.

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%, with descriptions for all 9 parameters. The description adds value through practical examples (e.g., corner sticker positioning) and clarifies response_format defaults.

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 a sticker/emoji overlay with positioning and transformation. It distinguishes from siblings like capcut_add_text and capcut_add_image through the specific resource and behavior.

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

Usage Guidelines3/5

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

The description implies usage via examples and defaults, but lacks explicit guidance on when to use this tool versus alternatives like capcut_add_text or capcut_add_image. No when-not-to-use or prerequisite information is 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/eery1677-lab/capcut-mcp'

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