Skip to main content
Glama

Motioneed

by com.motioneed
OverviewDiscussionsAdmin

Create a video

create_video

Start a motion video from a public product URL or a prompt. Returns at once with status "queued"; poll get_video until it is "ready", then give the user video_url (needs the API key) or call share_video for a public link; poster_url is its cover image. Spends credits.

Input Schema

NameRequiredDescriptionDefault
urlNoPublic page to read for the product, brand, colours and copy, e.g. https://your-product.com
modelNoWriting model id, or "auto" (default).
voiceNoAdd narration. Default false.
aspectNoFrame. Default 16:9; 9:16 for vertical social.
imagesNoUp to 10 screenshots or images (PNG, JPEG, WebP, GIF; 5 MB each). use "screen" (default) puts one on screen; "style" is a look to match, never shown.
promptNoOne or two sentences describing the video, used alone or with url.
purposeNoad (default), demo, or launch.
secondsNoLength in seconds. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / images
      Added value: +{
+  "description": "Up to 10 screenshots or images (PNG, JPEG, WebP, GIF; 5 MB each). use \"screen\" (default) puts one on screen; \"style\" is a look to match, never shown.",
+  "items": {
+    "properties": {
+      "data": {
+        "description": "Or the image as a data URL: data:image/png;base64,...",
+        "type": "string"
+      },
+      "name": {
+        "description": "What it shows, e.g. \"new billing page\".",
+        "type": "string"
+      },
+      "url": {
+        "description": "A public image URL.",
+        "type": "string"
+      },
+      "use": {
+        "enum": [
+          "screen",
+          "style"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does it well: it discloses the asynchronous queue-and-poll behavior, the credit spend, the API-key requirement for video_url, and the meaning of poster_url. That is exactly the behavioral context an agent cannot get from 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?

Front-loaded with the action, then the follow-up chain and cost. Every clause carries information, though the single semicolon-chained sentence is denser than ideal and could be split for readability.

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?

For an async creation tool with no output schema, the description supplies the return status, the poll target, the two ways to deliver the result, and the cover-image field. Nothing essential for correct invocation or follow-through is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so enum values, defaults, limits and nested image fields are already documented. The description only adds that url and prompt can be combined or used alone, which largely duplicates the schema's own wording, so the baseline 3 applies.

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?

States a specific verb and resource ('Start a motion video') plus the two accepted input modes (public product URL or prompt). The workflow mentions get_video and share_video, which positions it clearly against those siblings and implicitly against revise_video.

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 an explicit sequence: this call returns immediately as 'queued', poll get_video until 'ready', then surface video_url or call share_video for a public link. It also flags a prerequisite ('needs the API key') and a cost ('Spends credits'), so the agent knows when and how to use it.

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

All Motioneed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources