Skip to main content
Glama

Create Video

create_video
Destructive

Start a new video from a topic (10-1500 chars: subject, style, message, call to action). Multi-scene videos first get a script for review (free); nothing is rendered or billed until approve_script. single_scene=True makes one short clip (<=11s) that renders immediately and spends credits right away. aspect_ratio: '9:16' (vertical) or '16:9'. video_type: one of Fabeo's seven styles (see get_started); its style is written into the brief. reference_image_keys (from upload_reference_image / get_reference_upload_url) and/or reference_upload_id (from get_reference_upload_page, after the user uploaded): up to 5 images in total; every scene is then rendered to match them (the person's face/outfit, the product), so describe the person in the topic consistently with those images. product_id (from list_catalog): the video is for that product -- its description goes into the brief, and catalog_image_keys (from get_product) adds its stored photos as references.

Input Schema

NameRequiredDescriptionDefault
topicYesThe brief: subject, audience, style, key message and call to action. Describe any person consistently with the reference images.
product_idNoThe product (from list_catalog) the video is for. It is filed under it, and create_video writes the script from the product's own description too. Omit for the account's default product.
video_typeNoThe style: ugc_style = UGC-Style Content / Avatar (Looks like a real person filming on their phone — testimonial, unboxing, "get ready with me."); before_after = Before & After / Transformation (Split-screen or morph reveal — skincare, fitness, renovation, makeover.); product_demo = Product Demo / Showcase (Item rotating, zooming, "in use" shots for a listing or ad.); explainer = Explainer / How-To (A presenter walking through steps, or text-to-scene diagrams brought to life.); social_ad = Advertisement / Commercial (Short, high-energy hook clips for paid social — often stylized, exaggerated motion.); animation = Animation / Cartoon Video (A recurring animated character across the video.); cinematic_trailer = Cinematic Trailer / Brand Video (Mood pieces, fantasy/sci-fi concept trailers, pitch visuals.).explainer
aspect_ratioNo'9:16' vertical (Reels, TikTok, Shorts) or '16:9' horizontal (YouTube, web).9:16
single_sceneNoTrue: one short clip (<=11s) that skips script review, renders immediately and spends credits. False (default): multi-scene script for review first, free.
idempotency_keyNoA unique string for this request (e.g. a UUID). Reuse it when retrying: a repeat within 24h returns the first result instead of starting (and charging for) a second render.
duration_secondsNoTarget length in seconds (5-60; a single_scene video is capped at 11). The rendered length follows the narration, so this is approximate.
catalog_image_keysNoimage_key values of photos already stored on the product, its brand or client (from get_product) to use as reference images; needs product_id. No rights confirmation needed.
reference_upload_idNoupload_id from get_reference_upload_page, once the user has uploaded their photos there.
use_product_detailsNoWith product_id: add the product's title, description and brand to the brief (default). False to write from the topic alone.
reference_image_keysNoreference_image_key values from upload_reference_image / get_reference_upload_url (up to 5 images in total with reference_upload_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the money-relevant behavior: nothing is rendered or billed until approve_script, while single_scene spends credits immediately. That is the crucial hidden trait for a destructiveHint=true, non-idempotent mutation, and it is stated plainly rather than left to the agent to infer.

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?

The critical facts (script review vs immediate render, cost) are front-loaded in the first three sentences. It is dense and mostly earns its length, but it restates some schema content verbatim (aspect_ratio formats, video_type listing) which makes it longer than necessary.

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-parameter, no-output-schema creation tool it covers the workflow, cost model, and every input's provenance. The remaining gap is the return value: with no output schema, the agent is never told whether it receives a video_id, job_id, or script handle to pass to approve_script or get_job_status.

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 baseline is 3; the description earns extra by adding cross-parameter meaning the schema cannot express — the combined 'up to 5 images in total' cap across reference_image_keys and reference_upload_id, and the product_id + catalog_image_keys coupling. It also warns that people described in the topic must match the reference images.

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?

Opens with a specific verb+resource ('Start a new video from a topic') and immediately bounds it (10-1500 chars, subject/style/message/CTA). It also distinguishes itself from siblings by naming approve_script as the gate and by contrasting the single_scene path, so an agent can separate it from create_video_from_audio or create_from_template.

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?

Gives explicit when-to-use branches: multi-scene (default) for script-first free review, single_scene=True for an immediate <=11s clip. It names the prerequisite chains for every optional input (product_id from list_catalog, reference_image_keys from upload_reference_image, reference_upload_id from get_reference_upload_page) and points to get_started for video_type.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources