Vector Animation through MCP
Use vector_animation only when the user explicitly requests Vector Animation for formulas, algorithms, structures, or processes.
Pass catalog-valid arguments to kp_create_creation:
{ "type": "vector_animation", "prompt": "Use [3, 7, 12, 18, 25, 31, 42, 56, 68, 73, 88] to demonstrate binary search for 73, with accurate low, high, and mid labels in every round", "language": "en", "aspect_ratio": "16:9"}Do not send duration_seconds or scene_count. Read supported ratios, voices, and qualities from kp_get_catalog.
After generation, use kp_get_creation to inspect scenes and editable_actions before editing narration or regenerating one scene.
When to choose Vector Animation
Choose Vector Animation for information that has a precise visual grammar: a formula, algorithm, architecture, comparison, or process. Name the entities, their relationships, the order of operations, and the labels that must remain accurate. For an algorithm, include the input and the expected progression; for a system, identify the components and the direction of the flow.
Keep the request structurally specific
Do not use this type as a generic animation request. It works best when the prompt gives a small, reviewable structure rather than a broad topic. Read the catalog before choosing language, ratio, voice, or quality, and omit duration_seconds and scene_count, which do not belong to this product type.
The creation remains asynchronous. Poll the job ID from kp_create_creation, then use kp_get_creation to read the actual scene list and supported edits. If a label or explanation needs correction, use a supported scene action rather than assuming a new video is already available.
Continue from here
Quickstartfor the create-to-detail lifecycleExplainer Videofor narration-led continuous scenesAvailable Toolsfor the full MCP tool list