Skip to main content
Glama
luquimbo

DaVinci Resolve MCP Server

by luquimbo

clip_clear_flags

Destructive

Clear a specified flag color from a clip to remove visual markers and keep your DaVinci Resolve timeline organized.

Instructions

Remove a specific flag color from a clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYesFlag color to remove (e.g. "Blue").
clip_nameYesName of the clip.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds minimal context beyond the destructiveHint annotation by clarifying that it removes 'a specific' flag color, not all flags. However, it does not disclose other behavioral details such as whether the operation is reversible or what happens if the flag color is not found.

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 a single, front-loaded sentence that conveys the essential information efficiently. No wasted words.

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?

The tool is simple (2 params, no enums, output schema present), but the description lacks usage guidance and any caveats. Given the destructiveHint annotation, the description does not fully address the operational context, so a mid-range score is warranted.

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 coverage is 100% and both parameters (color, clip_name) are described in the schema. The description adds no additional semantic meaning beyond what the parameter descriptions already provide, so baseline 3 is appropriate.

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 'Remove a specific flag color from a clip' uses an imperative verb and clearly identifies the resource (clip) and the specific action (removing a flag color). It distinguishes itself from sibling tools like clip_clear_color or clip_add_flag by specifying 'flag color'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., clip must exist, flag color must be present) or contrast with clip_add_flag or clip_get_flags.

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/luquimbo/davinci-resolve-mcp'

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