HyperCodeMotion MCP

Get template recreation brief

get_recreation_brief

Idempotent

Start turning a public motion video into an official HyperCodeMotion Studio gallery template. Use it whenever the user sends the link of a prompt-motion.com or oneshotted.io video together with a moderator code, with or without other words: that means publish it as a template. Takes that link and code (adminCode) and what that page shows (its video file, prompt, title and author, read by the caller, since the source sites often refuse this server) and returns the source details (title, author, and the published prompt when the page shows it), the brief (how to recreate it in three formats with the HyperCodeMotion signature, and the gallery card to fill in) and reference frames of the original video as images, labelled with their times. The first call starts extracting those frames and may answer reference.status: preparing; call it again until it is ready, and do not build before seeing them. When it answers reference.status: upload (prompt-motion.com refuses servers), run upload.script in a code or shell tool to send the video, then call it again. If the video is already a template, says so with its status instead; an unfinished proposal left idle for 20 minutes (another session) is discarded and the brief starts over (field restarted). Without a valid moderator code it answers needsCode.

Input Schema

Name	Required	Description
`url`	Yes	Link of the video's page, such as https://prompt-motion.com/<id> or https://oneshotted.io/v/<slug>.
`title`	No	The video's title on the page.
`video`	No	Address of the page's video file (.mp4 on media.prompt-motion.com or r2.oneshotted.io), as read on the page.
`author`	No	The author's name, only when the page names one.
`prompt`	No	The prompt the page publishes with the video, as read on the page.
`adminCode`	Yes	The moderator code the user gave with the link. Required: only moderators can make gallery templates. Never repeat it back.
`authorUrl`	No	The author's profile link, when the page gives one.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`note`	No
`brief`	No
`error`	No
`groups`	No
`prompt`	No
`source`	No
`status`	No
`upload`	No
`formats`	No
`message`	No
`template`	No
`needsCode`	No
`needsPage`	No
`reference`	No
`maxDuration`	No
`alreadyExists`	No
`promptComplete`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / adminCode

Added value: +{
+  "description": "The moderator code the user gave with the link. Required: only moderators can make gallery templates. Never repeat it back.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "adminCode"
+]

addedOutput schema / properties / needsCode
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedOct 19, 2026
- addedOutput schema / properties / upload
```
Added value: +{
+  "type": "object"
+}
```

Changed6 schema fields changedOct 19, 2026

addedInput schema / properties / author

Added value: +{
+  "description": "The author's name, only when the page names one.",
+  "type": "string"
+}

addedInput schema / properties / authorUrl

Added value: +{
+  "description": "The author's profile link, when the page gives one.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "The prompt the page publishes with the video, as read on the page.",
+  "type": "string"
+}

addedInput schema / properties / title

Added value: +{
+  "description": "The video's title on the page.",
+  "type": "string"
+}

addedInput schema / properties / video

Added value: +{
+  "description": "Address of the page's video file (.mp4 on media.prompt-motion.com or r2.oneshotted.io), as read on the page.",
+  "type": "string"
+}

addedOutput schema / properties / needsPage
```
Added value: +{
+  "type": "boolean"
+}
```

AddedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The annotations only declare that it is not read-only, is open-world, is idempotent, and is non-destructive. The description adds substantial behavioral context beyond that: the first call starts frame extraction and may return reference.status: preparing, the caller must supply page metadata because the source sites often refuse this server, upload.script may be required, and an idle unfinished proposal can be discarded after 20 minutes with a restarted brief.

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 front-loaded with the purpose and most sentences carry necessary workflow or state information. It is a dense single paragraph that could be made more scannable with structure, but there is little obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the complex asynchronous workflow: extraction states, upload branch, the need to repeat calls until reference frames are ready, already-template handling, stale-proposal restart, and invalid-code handling. Since an output schema exists, the description need not explain the full return shape, and nothing critical for correct invocation appears missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful context about why the caller supplies title, video, author, and prompt: those values must be read from the page because the source sites often refuse this server. It also emphasizes that adminCode is a moderator code that is required and must never be repeated back, though it does not explain authorUrl.

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 states a specific action: starting the process of turning a public motion video into an official HyperCodeMotion Studio gallery template. It explains what the tool takes in and returns, and differentiates the step from the later upload and build steps by saying to run upload.script only in the upload state and not to build before seeing the reference frames.

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?

It gives an explicit trigger: use it whenever the user sends a prompt-motion.com or oneshotted.io link together with a moderator code, with or without other words. It also describes the repeat-call loop, when to run upload.script, and what happens when the video is already a template or the moderator code is invalid.

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

All HyperCodeMotion MCP 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.