Skip to main content
Glama

Add Visual Effect

capcut_add_effect

Apply visual effects such as blur, sharpen, brightness, contrast, saturation, vignette, grain, or glitch to specific video segments with adjustable intensity.

Instructions

Apply visual effects to video segments.

This tool adds effects like blur, sharpen, brightness adjustments, and more.

Args:

  • draft_id (string): The draft ID

  • effect_name (string): Effect to apply (blur, sharpen, brightness, contrast, saturation, vignette, grain, glitch)

  • start (number): Start time in seconds

  • end (number): End time in seconds

  • intensity (number): Effect intensity 0.0-1.0 (default: 0.5)

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

Examples:

  • Add blur: effect_name="blur", intensity=0.7

  • Increase brightness: effect_name="brightness", intensity=0.8

  • Add vignette: effect_name="vignette", intensity=0.4

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draft_idYesThe ID of the draft to add effect to
effect_nameYesName of the effect to apply
startYesStart time in seconds
endYesEnd time in seconds
intensityNoEffect intensity (0.0 to 1.0)
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 indicate this is a write operation (readOnlyHint false) but no destructive or idempotent info. The description adds no behavioral details beyond what the schema provides, such as whether effects stack or replace. It adequately describes the action but does not enhance transparency beyond annotations.

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, well-structured with Args and Examples sections. Every sentence adds value, and the main purpose is front-loaded.

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 complexity (6 params) and no output schema, the description provides examples and covers all parameters. It lacks information on return values or side effects, but for a straightforward apply-effect tool, it is nearly complete.

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 description coverage is 100%, so parameters are well-documented. The description repeats parameter info and provides examples, adding marginal value. Baseline 3 is appropriate as it does not significantly expand on the schema.

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 title and description clearly state the tool applies visual effects to video segments, listing specific effects like blur, sharpen, brightness. This distinguishes it from sibling tools that add audio, images, 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 implies when to use this tool (for visual effects on video segments) and excludes alternatives like adding audio or images. It does not explicitly state when not to use, but context from sibling tools makes it clear.

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