Digital Maker AI

preview_single_image

Generate the one held image a Single Scene video is built around: a large close portrait of the subject on one side of the frame, the rest of the scene falling softly out of focus so the captions can sit over it. Show it to the user and let them confirm or ask for another before you call create_video. This is the cheap confirm gate: it creates no job, spends no video minutes and does not touch the daily limit, so redoing it is fine. Pass the returned image_url plus the SAME face_side to create_video with format single.

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": "preview_single_image"
  }
}

Input Schema

Name	Required	Description
`topic`	No	What the video is about. Used to invent a subject who fits it. Give this or background.
`subject`	No	What the subject looks like, in plain English: who or what they are, age, build, clothing, expression. Optional; without it a person who fits the topic is invented. Stoic topics always get an ancient marble statue whatever is passed here. With a character, this only styles them.
`character`	No	Name of a saved character to use as the subject, so the held image is recognisably them. Optional.
`face_side`	No	Which side the subject stands on. Captions go on the other side. Defaults to left.
`background`	No	The setting to place them in, in plain English. Optional; without it a setting that fits the topic is invented.
`style_preset`	No	Visual world for the image. Defaults to cinematic_documentary.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / subject

Added value: +{
+  "description": "What the subject looks like, in plain English: who or what they are, age, build, clothing, expression. Optional; without it a person who fits the topic is invented. Stoic topics always get an ancient marble statue whatever is passed here. With a character, this only styles them.",
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it states that this creates no job, spends no video minutes, and does not touch the daily limit, so redoing it is safe. It also mentions the returned image_url and the need to reuse the same face_side, though it does not describe the full response shape.

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 description is four compact sentences, front-loads the purpose, and includes only actionable guidance: composition, confirmation flow, cost profile, and next-step linkage. Every sentence earns its place.

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 six-parameter tool with no annotations and no output schema, the description covers what is generated, how to use the result, the cost/side-effect profile, and the key return value. The input schema already supplies rich parameter details, so the description needs no further expansion.

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 already 100%, so the schema documents all six parameters. The description still adds practical meaning by tying face_side to create_video and warning to pass the SAME face_side, which is workflow semantics beyond the schema.

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: generating the one held image for a Single Scene video, and even describes the intended composition. It clearly separates this preview image from the later create_video step, so an agent knows exactly what this tool produces.

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?

It gives clear usage context: show the result to the user for confirmation or another attempt before calling create_video. It does not explicitly compare against alternatives such as generate_image, but the workflow condition is unambiguous.

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?