Digital Maker AI

list_video_scenes

Read-onlyIdempotent

The scenes of one of the user's finished videos, numbered from 1, each with its narration line and picture, plus how many animated scenes the user has left. Use it when the user wants to animate scenes (make them move) or edit scenes (regenerate_scene_image, set_scene_image, update_video), to show them what there is to pick from; each picture link can also be downloaded. Suggest a few scenes that would look best moving (clear action, landscapes, vehicles, weather, crowds) if they want a recommendation. Long videos have many scenes: page through with from. Reads only, costs nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_video_scenes"
  }
}

Input Schema

Name	Required	Description
`from`	No	First scene number to list. Defaults to 1.
`count`	No	How many scenes to list, up to 60. Defaults to 20.
`video_id`	No	The video's id from check_video or list_creations. Omit for the most recent finished video.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful operational context: it costs nothing, long videos require paging with `from`, and picture links can be downloaded. That is meaningful behavioral information 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?

The definition is front-loaded with what the tool returns, then usage guidance, recommendation advice, pagination, and cost/safety notes. Despite being fairly dense, each sentence contributes useful information without repetition.

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?

No output schema exists, so the description carries the burden of explaining returned content, and it does so clearly: numbered scenes, narration, picture links, and remaining animated scene count. Combined with annotations and schema, an agent has enough information to invoke it correctly.

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 100%, so all three parameters are already well documented. The description mentions paging with `from`, but does not add format, default, or edge-case semantics beyond what the schema provides; baseline 3 is appropriate.

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 states a specific verb and resource: listing scenes of one of the user's finished videos, including scene numbers, narration, pictures, and remaining animated scenes. It clearly distinguishes this listing tool from siblings such as check_video and list_creations by describing exactly what is returned.

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 gives explicit trigger conditions: when the user wants to animate or edit scenes, and it names the relevant downstream tools (regenerate_scene_image, set_scene_image, update_video). It also explains pagination with `from` and even when to offer scene recommendations.

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

All Digital Maker AI 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?