Removes a scene by index or name along with every clip in its row. Destructive action—confirm with the user first; a set always keeps at least one scene.
Delete a scene (index or name) together with every clip in its row. Destructive: confirm with the user before deleting their material. A set keeps at least one scene.
| Name | Required | Description | Default |
|---|---|---|---|
| scene | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds non-obvious behavior: cascading deletion of all clips in the scene's row and the minimum-one-scene constraint, which the annotations do not convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the action and cascade behavior, followed by the destructive warning and the invariant. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema is needed for a delete tool, and annotations cover the safety hints. The description supplies cascade scope, the confirmation requirement, and the one-scene invariant; only error/edge-case behavior on an invalid scene reference is unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. Stating the scene may be given as 'index or name' explains the schema's anyOf (integer|string) meaningfully, though it doesn't say how names are resolved or what happens on ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Delete) and resource (a scene), and clarifies scope as 'together with every clip in its row,' which distinguishes it from siblings like delete_clip and delete_track. An agent can tell immediately what is removed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs confirmation before deleting user material and states the business constraint that a set must retain at least one scene. It doesn't name an alternative or an explicit when-not condition, but the context is clear enough to route correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.