Skip to main content
Glama

Create a video from a template

create_video_from_template

Create a Synthesia video by filling a STUDIO template's variables. Validates keys, auto-escapes text, and returns video ID for progress tracking.

Instructions

Create a Synthesia video from a STUDIO template by substituting its variables (templateData). The server fetches the template first and validates every templateData key against its declared variables — variable names are case-sensitive. Text values are HTML-entity-escaped automatically (Synthesia requirement); media variables accept an uploaded asset ID or a URL. DEFAULTS TO A FREE DRAFT (watermarked); pass render_mode='final' only on explicit approval. Returns a videoId immediately; check progress with get_video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateIdYesTemplate ID (see list_templates).
templateDataYesVariable name → value. Keys are CASE-SENSITIVE and must match the template's variables exactly.
titleNoDefaults to the template title.
descriptionNo
visibilityNo
ctaSettingsNo
brandKitIdNo'workspace_default' behavior if unset; 'no_brand_kit' to disable branding; or a custom brand kit UUID.
folderIdNo
callbackIdNoAuto-stamped if omitted.
escapeTextNoDefault true: HTML-escape string values (recommended). Set false ONLY if you are passing pre-escaped entities.
render_modeNodraft (DEFAULT): free test render with a watermark, does not consume the Synthesia quota — use for all iteration. final: full-quality render that COUNTS AGAINST the account's video quota — only use when the user explicitly approves a final render.
Behavior4/5

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

With no annotations, the description details critical behaviors: server-side validation, case sensitivity, HTML escaping, media handling, draft default, and async return. Missing rate limits or error handling, but sufficient for operation.

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

Conciseness4/5

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

Concise and well-structured: front-loaded purpose, then key details in separate sentences. Slightly long but every sentence adds value.

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 an 11-param tool with nested objects and no output schema, the description covers the core flow: template validation, variable substitution, draft default, return of videoId, and follow-up with get_video. Lacks error scenarios but adequate.

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?

Adds significant meaning beyond schema: explains templateData substitution, case sensitivity, media asset types, render_mode semantics, and brandKitId options. Some params like folderId lack extra context, but key parameters are well-documented.

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 clearly states the verb 'Create' and the resource 'Synthesia video from a STUDIO template', distinguishing it from sibling tools like 'create_video' which likely creates from scratch.

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?

Provides explicit guidance on default draft mode and when to use 'final' with approval. Implicitly differentiates from other tools by focusing on templates, but does not explicitly state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/keithazz/synthesia-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server