Digital Maker AI

list_video_options

Read-onlyIdempotent

THE VIDEO MAKER PANEL: in apps that show panels (Claude, ChatGPT) this opens the whole video maker as a form, like the website: format, topic or own script, length, style, voice with samples, captions, music, effects, recurring character, AI presenter, and a Make the video button; nothing is made until the user presses it. Call it whenever the user asks to open the video maker, wants to see or choose the options, or asks for 'all options', and pass what they already said as the prefill fields so the form starts filled in. Do not retype the options as a table when the panel is shown; say one sentence and let them use it. In apps without panels the text answer lists everything instead. Everything create_video can be set to, filtered to what this user's plan actually allows: orientations, formats, length ceiling, visual styles, subtitle styles, paces, languages and the full voice catalogue. Call this before making a video when the user wants to choose rather than have you decide, when they ask what voices or styles exist, or when you are about to guess at a value. It reads nothing and 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_options"
  }
}

Input Schema

Name	Required	Description
`music`	No	Prefill: a music mood or track.
`topic`	No	Prefill for the panel: what the user said the video is about.
`voice`	No	Prefill: a voice name they mentioned.
`format`	No	Prefill: the format they asked for.
`section`	No	Narrow the answer. Defaults to all. 3d = everything about 3D Animated films: minutes left, packs, presets, Storyteller voices, song options.
`language`	No	Prefill: narration language.
`character`	No	Prefill: the saved character they want to use.
`orientation`	No	Prefill: vertical if they asked for a Short.
`style_preset`	No	Prefill: the style, e.g. the one their character was made for.
`voice_accent`	No	Only list voices with this accent (ES, FR, IT, DE are the native Spanish, French, Italian and German voices).
`voice_gender`	No	Only list voices of this gender.
`subtitle_style`	No	Prefill: captions.
`duration_minutes`	No	Prefill: the length they asked for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / voice_accent / description

Previous value: -"Only list voices with this accent (ES-LA, ES, FR, IT, DE are the native Spanish, French, Italian and German voices)."New value: +"Only list voices with this accent (ES, FR, IT, DE are the native Spanish, French, Italian and German voices)."

changedInput schema / properties / voice_accent / enum

Previous value: -[
-  "US",
-  "UK",
-  "AU",
-  "ES-LA",
-  "ES",
-  "FR",
-  "IT",
-  "DE",
-  "Standard"
-]New value: +[
+  "US",
+  "UK",
+  "AU",
+  "ES",
+  "FR",
+  "IT",
+  "DE",
+  "Standard"
+]

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / voice_accent / description

Previous value: -"Only list voices with this accent."New value: +"Only list voices with this accent (ES-LA, ES, FR, IT, DE are the native Spanish, French, Italian and German voices)."

changedInput schema / properties / voice_accent / enum

Previous value: -[
-  "US",
-  "UK",
-  "AU",
-  "Standard"
-]New value: +[
+  "US",
+  "UK",
+  "AU",
+  "ES-LA",
+  "ES",
+  "FR",
+  "IT",
+  "DE",
+  "Standard"
+]

Changed10 schema fields changedNov 4, 2026

addedInput schema / properties / character

Added value: +{
+  "description": "Prefill: the saved character they want to use.",
+  "type": "string"
+}

addedInput schema / properties / duration_minutes

Added value: +{
+  "description": "Prefill: the length they asked for.",
+  "maximum": 60,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / format

Added value: +{
+  "description": "Prefill: the format they asked for.",
+  "enum": [
+    "multi",
+    "single",
+    "whiteboard"
+  ],
+  "type": "string"
+}

addedInput schema / properties / language

Added value: +{
+  "description": "Prefill: narration language.",
+  "enum": [
+    "en",
+    "fr",
+    "es",
+    "it",
+    "de"
+  ],
+  "type": "string"
+}

addedInput schema / properties / music

Added value: +{
+  "description": "Prefill: a music mood or track.",
+  "type": "string"
+}

addedInput schema / properties / orientation

Added value: +{
+  "description": "Prefill: vertical if they asked for a Short.",
+  "enum": [
+    "landscape",
+    "vertical"
+  ],
+  "type": "string"
+}

addedInput schema / properties / style_preset

Added value: +{
+  "description": "Prefill: the style, e.g. the one their character was made for.",
+  "enum": [
+    "cinematic_documentary",
+    "animated_cartoon",
+    "motivational_dark",
+    "finance_luxury",
+    "history_ancient",
+    "space_scifi",
+    "minimalist_clean"
+  ],
+  "type": "string"
+}

addedInput schema / properties / subtitle_style

Added value: +{
+  "description": "Prefill: captions.",
+  "enum": [
+    "none",
+    "clean",
+    "boxed",
+    "yellow",
+    "pop",
+    "minimal"
+  ],
+  "type": "string"
+}

addedInput schema / properties / topic

Added value: +{
+  "description": "Prefill for the panel: what the user said the video is about.",
+  "type": "string"
+}

addedInput schema / properties / voice

Added value: +{
+  "description": "Prefill: a voice name they mentioned.",
+  "type": "string"
+}

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / section / description

Previous value: -"Narrow the answer. Defaults to all."New value: +"Narrow the answer. Defaults to all. 3d = everything about 3D Animated films: minutes left, packs, presets, Storyteller voices, song options."

changedInput schema / properties / section / enum

Previous value: -[
-  "all",
-  "voices",
-  "styles",
-  "formats"
-]New value: +[
+  "all",
+  "voices",
+  "styles",
+  "formats",
+  "3d"
+]

First observedOct 17, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so "It reads nothing and costs nothing" largely restates them. The genuinely additive disclosures are environmental behavior (form panel where panels exist, full text listing elsewhere) and "nothing is made until the user presses it", which tells the agent the call itself has no side effect on the user's project. Beyond that it says nothing about response shape, size of the returned catalogue, or latency for the large voice catalogue.

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

Conciseness3/5

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

It is front-loaded with the key framing sentence, but the body is a semicolon-chained run-on that mixes panel mode, prefill guidance, sibling ordering and the returned catalogue into a single wall of text. The closing enumeration of what create_video can be set to partially repeats the enumeration in the opening sentence.

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 13-parameter, zero-required, side-effect-free options tool with no output schema, the description covers both execution modes, the trigger conditions, the prefill contract and the plan-filtering caveat. What is missing is any sense of what the text-mode answer looks like or how large it is, which matters when the agent must decide whether to surface it inline.

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% and every one of the 13 parameters already carries a "Prefill: ..." or filter description, so the baseline is 3. The description adds only the general framing that supplied values prefill the form and that the catalogue is filtered to the user's plan limits, without clarifying semantics for any individual field such as how section interacts with the prefill parameters.

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 VIDEO MAKER PANEL" plus a concrete enumeration of what the form contains (format, topic, length, style, voice, captions, music, effects, recurring character, AI presenter) states a specific resource and scope, and the description explicitly positions itself against create_video ("everything create_video can be set to"). It also discloses the dual mode (panel form vs. text list) so the agent knows what it is actually invoking.

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 positive triggers ("when the user asks to open the video maker, wants to see or choose the options, or asks for 'all options'"; "when they ask what voices or styles exist, or when you are about to guess at a value") and an explicit negative/alternative rule ("Do not retype the options as a table when the panel is shown"). It also prescribes the ordering relative to a sibling: call this before create_video when the user wants to choose.

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?