Kuro

Set a scene's still

set_scene_image

Destructive

Use an image the account already holds — a generation or an upload — as one scene's still, replacing the one it has. To make a new still instead, use generate_scene_images. 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>",
      "scene": "<scene>",
      "reference": "<reference>"
    },
    "name": "set_scene_image"
  }
}

Input Schema

Name	Required	Description	Default
`scene`	Yes
`reference`	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.7/5.0

Behavior5/5

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

Annotations already mark the tool destructive and non-idempotent, but the description adds valuable context: it replaces the scene's current still, is undoable via undo_storyboard in one step, and spends no credits. This is rich behavioral disclosure beyond the annotations.

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 compact sentences, front-loaded with the core action. Each sentence adds useful information: scope, alternative, undo behavior, and credit cost.

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 hints and an output schema present, the description supplies what an agent needs to select and invoke correctly: source of image, replacement behavior, alternative for new generation, undo path, and cost. Nothing critical 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 must carry parameter meaning. It helpfully clarifies that the image reference may be an existing generation or upload and that the target is a single scene, but it does not explicitly explain storyboard_id, the scene index semantics, or the required reference discriminator structure.

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: use an existing account-held image as one scene's still, replacing the current one. It explicitly distinguishes itself from generate_scene_images, so an agent can tell the two apart without inspecting schemas.

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?

Gives clear when-to-use guidance: existing generation or upload for this tool, while creating a new still should use generate_scene_images. It also names the undo path, leaving no ambiguity about alternatives.

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?