Simpler.Asia

studio.add_scene_from_asset

Append an uploaded video or image asset to the main track as a finished scene, or insert it at at_index. Assets longer than 10 minutes become consecutive scenes. A video with no measured length lands as one untrimmed 5s scene marked length_estimated: true, here and in get_composition, until the file is measured in the studio editor. Audio assets are refused; use add_audio_to_timeline.

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>",
      "asset_id": "<asset_id>"
    },
    "name": "studio.add_scene_from_asset"
  }
}

Input Schema

Name	Required	Description
`asset_id`	Yes	A video or image asset id (vas_...) from get_composition's assets list.
`at_index`	No	0-based position in scene order; appends when omitted.
`project_id`	Yes	The studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the lone readOnlyHint:false annotation, the description discloses concrete behavior: assets over 10 minutes split into consecutive scenes, unmeasured videos land as one untrimmed 5s scene flagged length_estimated:true (visible here and in get_composition) until measured, and audio assets are rejected. That is real non-obvious behavioral context not available in structured fields.

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?

Four tight sentences, no filler, front-loaded with the core action before the edge-case rules (duration split, 5s fallback, audio refusal). Every sentence conveys a distinct constraint.

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?

For a mutation tool with no output schema, the description covers the essentials: what gets created, how long assets are split, the length_estimated fallback and where it propagates, and the sibling alternative for audio. An agent can invoke this correctly without further inference.

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 coverage is 100%, so asset_id, at_index, and project_id are already documented, and the description's mention of 'insert at at_index' merely restates the schema's 'appends when omitted' semantics. Baseline 3 is appropriate since the schema carries parameter meaning.

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 names a specific verb and resource – append an uploaded video/image asset to the main track as a finished scene, or insert at at_index – and names the composed result (scene). An agent can tell it apart from generic studio.add_scene because the source object (an uploaded asset) is explicit.

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?

Usage is defined positively (use uploaded video/image assets), positionally (append vs insert at at_index), and negatively with a named alternative: 'Audio assets are refused; use add_audio_to_timeline.' That is explicit when/when-not guidance with a sibling handoff.

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?