Simpler.Asia

studio.generate_scene

[$0.10/sec at provider cost] Generate video for a scene from its prompt (text-to-video). Pass scene_id to fill a planned scene, or prompt to create-and-generate in one step. NEVER mention camera equipment (crane, dolly, rig) — describe what to SHOW. Say 'camera rises' NOT 'crane shot'. Include: subject, action, lighting, color palette, mood.

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": {
      "project_id": "<project_id>"
    },
    "name": "studio.generate_scene"
  }
}

Input Schema

Name	Required	Description	Default
`style`	No	Visual style: cinematic, corporate, playful, dramatic	cinematic
`prompt`	No	Visual description; required when scene_id is omitted.
`scene_id`	No	Planned scene to generate (optional).
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`duration_seconds`	No	Whole seconds (3-10).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds real context beyond the single readOnlyHint=false annotation: the $0.10/sec provider cost, which lets an agent reason about spend before invoking. The prompt-writing constraints are also operational behavior not captured anywhere in the schema. It stops short of saying whether generation is synchronous, how long it takes, or what is returned, which matters for a paid job.

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

Conciseness4/5

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

Cost and purpose are front-loaded, followed by mode selection and prompt guidance. The camera-equipment aside takes three short clauses where one would do, but each sentence carries actionable content and nothing is redundant.

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?

For a mutation tool with no output schema and minimal annotations, the description covers cost, mode selection, and prompt content — enough to invoke it well. It omits return behavior and timing (async job vs inline result), the main remaining gap for a generation call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by framing scene_id and prompt as mutually exclusive generation modes — more precise than the schema's terse 'required when scene_id is omitted' — and defines the content the prompt must contain (subject, action, lighting, palette, mood).

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 ('Generate video for a scene from its prompt (text-to-video)') and disambiguates the two modes via scene_id vs prompt. An agent can distinguish this from studio.add_scene or image.generate without opening a schema.

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?

Gives explicit branch conditions: pass scene_id to fill an already planned scene, or prompt to create-and-generate in one step. Clear on when each parameter path applies, though it does not name sibling alternatives (e.g. image.generate or studio.request_regeneration) for adjacent needs.

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

All Simpler.Asia 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?