Skip to main content
Glama

effect_vignette

Apply a vignette effect to darken video edges, drawing focus to the center frame. Control darkness, radius, and smoothness.

Instructions

Apply vignette effect - darkened edges.

Creates a darkened border effect that draws attention to the center of the frame.

Args: input_path: Absolute path to input video. output_path: Absolute path for output video. intensity: Darkness amount 0-1. Default 0.5. radius: Vignette radius 0-1 (1 = edge of frame). Default 0.8. smoothness: Edge softness 0-1. Default 0.5.

Returns: Dict with success status and output_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathYes
output_pathNo
intensityNo
radiusNo
smoothnessNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the effect (darkened edges), parameters, and return value. It does not mention any destructive actions or permissions, but the behavior is clear and non-contradictory.

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 with a front-loaded purpose, followed by clear parameter documentation. Every sentence adds value, and there is no redundant or unnecessary information.

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

Completeness5/5

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

Given the simplicity of the tool and presence of an output schema, the description is complete. It covers all inputs and the return value (Dict with success status and output_path), leaving no gaps for an agent to invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the Args section in the description explains each parameter's meaning, range, and default values (e.g., intensity 0-1, radius 0-1, smoothness 0-1). This fully compensates for the schema gap.

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 'Apply vignette effect - darkened edges' and explains it creates a darkened border that draws attention to the center. This distinguishes it from sibling effects like chromatic aberration or glow.

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?

The description does not provide any guidance on when to use this tool versus other effect tools or alternatives. It only describes what the tool does without context for selection.

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/KyaniteLabs/mcp-video'

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