VideoGen MCP

Official

Overview Schema Source Related Servers Discussions Admin

Slideshow to video

slideshow_to_video

Convert an uploaded PDF or slideshow into an editable narrated video. Provide the file ID, optionally add slide scripts, voice, language, aspect ratio, or an avatar narrator.

Instructions

Build an editable narrated video from an uploaded PDF or slideshow file. Upload the file first with upload_file, then pass its fileId. For avatar narration, pass actorEntityId and optionally set avatarQuality.

Input Schema

TableJSON Schema

Name	Required	Description
`fileId`	Yes	Uploaded PDF or slideshow file id.
`voiceId`	No	Catalog display name (e.g. Matilda) or voice id from list_tts_voices.
`language`	No	Output language as a BCP-47 code, such as en, es, or fr.
`autoExport`	No	When true (the default), the run stays in progress until an MP4 is ready. Use downloadUrl from the result. Set false only if you will call remix_project and then export_project yourself.
`aspectRatio`	No	Output aspect ratio as width:height units (not pixels). Example: { width: 16, height: 9 }.
`slideScripts`	No	Optional narration for each slide, in order.
`actorEntityId`	No	Id of an ACTOR entity (vg_enti_...) with an image reference. When set, narration is delivered by that actor avatar.
`avatarQuality`	No	Avatar generation quality tier. Applies when actorEntityId is provided. Omit to use workspace settings.
`slideshowThemeEntityId`	No	Optional id of a SLIDESHOW_THEME entity (vg_enti_...) whose reference board defines the shared slide design system. Omit when converting an uploaded deck's original pages; VideoGen derives a theme from those pages in the background.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Error details when status is failed; otherwise null.
`status`	No	Job status: pending, running, succeeded, failed, or cancelled.
`exportId`	No	Export id when autoExport succeeded (vg_expo_...).
`projectId`	Yes	Project created for this exact workflow attempt (vg_proj_...). A retry creates a different project.
`projectUrl`	Yes	Deep link to the project created for this exact workflow attempt. Keep it paired with workflowRunId; a retry returns a new URL.
`downloadUrl`	No	Signed MP4 download URL when autoExport succeeded. Give this to the user.
`attemptIndex`	No	Current or latest attempt index.
`exportFileId`	No	File id of the rendered MP4 when autoExport succeeded.
`workflowType`	No	Workflow type (present after polling).
`workflowRunId`	Yes	Workflow run id (vg_work_...). Keep it paired with this response's projectId and projectUrl; a retry returns a new tuple.
`remixActionIds`	No	Remix action ids from the start response (empty when none requested).
`progressPercentage`	No	Completion progress 0-100 (present after polling).
`downloadUrlExpiresAt`	No	Unix expiry for downloadUrl.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Oct 2, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare the write/mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so safety is covered. The description adds the useful prerequisite ordering and notes the output is 'editable,' but says nothing about async behavior, runtime, or cost beyond what autoExport in the schema already conveys.

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?

Two tight sentences: purpose first, then the actionable prerequisite and the optional avatar path. No filler or restated field lists.

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?

With a rich 9-parameter schema, an output schema, and annotations, the description only needs to orient the agent — which it does by naming the required upload step. It stops short of routing among the numerous video-generation siblings, but otherwise nothing essential to invocation is missing.

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 every parameter including actorEntityId, avatarQuality, aspectRatio, and autoExport is already documented at the source. The description only restates the fileId prerequisite and the actorEntityId/avatarQuality pairing, adding little beyond the schema; baseline 3 applies.

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 ('Build') and resource ('editable narrated video') with the required source ('uploaded PDF or slideshow file'). This clearly separates it from siblings like script_to_video, voiceover_to_video, and storyboard_to_video.

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 a concrete prerequisite sequence ('Upload the file first with upload_file, then pass its fileId') and a conditional path for avatar narration. It does not, however, contrast this tool against the many other video-generation siblings, so the agent must infer when a slideshow source is the right choice.

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

Deploy Server