Skip to main content
Glama

delete_clip

Remove a clip from a CapCut timeline by providing the project name and segment ID.

Instructions

Delete a clip from the timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
segment_idYesID of the segment to delete.
project_nameYesName of the CapCut project.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'delete' without disclosing side effects (irreversible? frees resources?). This lack of behavioral context increases risk for an AI agent.

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

Conciseness3/5

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

The description is only one sentence, which is concise but omits necessary behavioral and usage information. Conciseness should not come at the cost of completeness; here it sacrifices guidance.

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

Completeness2/5

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

Given the tool's simplicity (2 params, output schema exists), the description still lacks important context like whether deletion is immediate/permanent or if any undo mechanism exists. This is incomplete for safe agent usage.

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 the parameter descriptions in the schema are clear ('ID of the segment to delete', 'Name of the CapCut project'). The description adds no extra meaning beyond the schema, so baseline score of 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 clearly states the action and resource: 'Delete a clip from the timeline.' It uses a specific verb ('delete') and resource ('clip'), and distinguishes well from sibling tools like trim_clip, split_clip, or move_clip.

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 on when to use this tool versus alternatives. It does not mention prerequisites (e.g., open project, existing clip) or when not to use it, which is needed for such a destructive operation.

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/baizo7/capcut_MCP_server-'

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