Kuro

Remove a sound card

remove_storyboard_sound

Destructive

Take one sound card off a film, by its number in sounds or its id. The audio stays in the library. One undo step; undo_storyboard takes it back. Spends no credits.

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>",
      "sound": "<sound>"
    },
    "name": "remove_storyboard_sound"
  }
}

Input Schema

Name	Required	Description	Default
`sound`	Yes
`storyboard_id`	Yes

Output Schema

Name	Required	Description	Default
`cast`	Yes
`brief`	Yes
`notes`	Yes
`quote`	No
`texts`	Yes
`scenes`	Yes
`sounds`	Yes
`videos`	Yes
`credits`	Yes
`history`	Yes
`message`	Yes
`skipped`	No
`started`	No
`stopped`	No
`accepted`	No
`receipts`	No
`schedule`	Yes
`settings`	Yes
`reference`	No
`storyboard`	Yes
`download_url`	No
`generation_id`	No
`remaining_scenes`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent behavior, but the description adds important specifics beyond them: only the storyboard card is removed, the source audio stays in the library, the action is one undo step, undo_storyboard reverses it, and no credits are spent.

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?

Three short sentences, with the action and scoping front-loaded and no redundant restatement. The undo and credit information is compact and useful.

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

Completeness4/5

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

The tool has an output schema, and annotations cover safety signals, so the description does not need to explain return values. It covers removal scope, asset retention, undo behavior, and credit cost, but leaves storyboard_id semantics only implied rather than stated.

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 must carry parameter meaning. It does well for the 'sound' parameter by explaining that it can be a number in sounds or an id, but it only implies storyboard_id via 'a film' and does not explicitly define that parameter.

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?

States a specific verb and resource: 'Take one sound card off a film.' It also clarifies that the target can be addressed by index in sounds or by id, which makes the operation distinguishable from add/update siblings.

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

Usage Guidelines4/5

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

Explains that the audio remains in the library and that undo_storyboard reverses the action, giving clear context for when this tool is appropriate. It does not explicitly compare with update_storyboard_sound or add_storyboard_sound, so it falls short of full alternative-routing guidance.

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?