Kuro

Delete storyboard

delete_storyboard

Destructive

Delete a film for good — the board, its scenes, its history — and stop anything it is still rendering or filming. Clips and stills already exported to the Library survive. Prefer update_storyboard with archived: true, which is reversible, unless the user asked for deletion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "storyboard_id": "<storyboard_id>"
    },
    "name": "delete_storyboard"
  }
}

Input Schema

Name	Required	Description	Default
`storyboard_id`	Yes

Output Schema

Name	Required	Description	Default
`message`	Yes
`deleted_storyboard_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag the operation as destructive and non-idempotent, but the description adds crucial behavioral context beyond them: what is destroyed (board, scenes, history), what side effects occur (stopping any active rendering or filming), and what survives (exported clips and stills in the Library). This is a clear value-add over the structured hints.

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?

Two tightly written sentences with zero waste. The destructive scope is front-loaded, followed immediately by the survival caveat and the preferred reversible alternative.

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?

With annotations covering safety and an output schema covering return values, the description supplies the remaining critical context: destruction scope, side effects on active work, data retention, and the safer alternative. Nothing an agent needs in order to call this correctly is missing.

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 0%, so the description would ideally clarify the single required parameter. It does not mention storyboard_id at all. However, the parameter name is self-explanatory and the schema specifies its UUID format, so the gap is small enough that the description does not actively mislead.

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 uses a precise verb ('Delete') and resource ('a film / the board'), and spells out the scope of what is removed: the board, its scenes, and its history. It also distinguishes the outcome from deletion of exported assets, so an agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the preferred alternative ('update_storyboard with archived: true') and states the condition under which deletion is appropriate ('unless the user asked for deletion'). This is exactly the when/when-not/alternative guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kuro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?