UX Pilot

make_video

Make or change a UX Pilot video (product reel, ad, explainer, social clip, logo animation) from a brief: purpose, audience, message, length, aspect (16:9, 9:16 or 1:1), brand and style. motionId changes a video. Credits. Poll get_job, then export kind video.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "make_video"
  }
}

Input Schema

Name	Required	Description
`pageId`	No	The page a new video goes on. Omit for a new page.
`params`	No	The action's fields. guide({ topic: "<tool>.<action>" }) lists them.
`prompt`	Yes	The brief, or what to change and keep.
`motionId`	No	A video to change, from get_job's motions.
`confirmed`	No	true only after the user agreed to this call.
`confirmationToken`	No	The token the first call answered with.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations' mutation and open-world signals, the description discloses credit usage and an asynchronous job workflow requiring polling and a separate export step. However, the terse 'Credits.' statement does not explain when or how many credits are consumed, and the confirmation flow is left to the schema.

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 description is compact and front-loads the operation, resource, and input brief before covering editing and workflow. Its fragments, especially 'Credits.' and 'export kind video,' are slightly cryptic but still convey useful information without substantial waste.

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 a complex tool without an output schema, it covers the main creation, modification, polling, and export lifecycle while the schema documents the individual parameters. The main remaining gaps are a clearer explanation of credit consumption and how the first-call confirmationToken and confirmed parameters fit into the invocation sequence.

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?

Although schema description coverage is 100%, the description adds useful prompt semantics by listing purpose, audience, message, length, brand, and style, plus supported aspect ratios. It also reinforces the distinct creation and modification roles of prompt and motionId.

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 that the tool makes or changes UX Pilot videos and gives concrete examples such as product reels, ads, explainers, and logo animations. Its video-specific scope distinguishes it from broader siblings such as design, edit, and generate_media.

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 explains that a brief drives creation, that motionId selects the change-an-existing-video workflow, and that the agent should poll get_job before exporting with kind video. It does not explicitly say when to choose a sibling tool instead or list exclusions.

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

All UX Pilot tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.