Skip to main content

Alpy

Overview Discussions Admin

Check an Alpy video

get_video

Read-onlyIdempotent

Where a video is: its status, progress, and, once made, links to the free preview and the finished video (valid for an hour). Says what to do next. Needs a connected Alpy account or an Alpy API key.

Input Schema

Name	Required	Description	Default
`id`	Yes	The id create_video returned.

Output Schema

Name	Required	Description	Default
`id`	Yes
`next`	Yes	What to do next, in words.
`title`	Yes
`status`	Yes	audio_ready, transcribing, character_selection, character_generating, plan_review, preview_generating, preview_ready, full_generating, ready or failed.
`seconds`	Yes	Length of the video.
`progress`	Yes	0 to 100.
`image_url`	Yes	The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.
`video_url`	Yes	The finished MP4, valid for an hour.
`studio_url`	Yes
`working_on`	Yes
`preview_url`	Yes	The free 10-second preview, valid for an hour.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / image_url

Added value: +{
+  "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "next",
-  "title",
-  "progress",
-  "working_on",
-  "seconds",
-  "preview_url",
-  "video_url",
-  "studio_url"
-]New value: +[
+  "id",
+  "status",
+  "next",
+  "title",
+  "progress",
+  "working_on",
+  "seconds",
+  "preview_url",
+  "video_url",
+  "studio_url",
+  "image_url"
+]

Changed2 schema fields changedOct 20, 2026

removedOutput schema / properties / image_url

Removed value: -{
-  "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "next",
-  "title",
-  "progress",
-  "working_on",
-  "seconds",
-  "preview_url",
-  "video_url",
-  "studio_url",
-  "image_url"
-]New value: +[
+  "id",
+  "status",
+  "next",
+  "title",
+  "progress",
+  "working_on",
+  "seconds",
+  "preview_url",
+  "video_url",
+  "studio_url"
+]

Changed2 schema fields changedOct 19, 2026

addedOutput schema / properties / image_url

Added value: +{
+  "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "next",
-  "title",
-  "progress",
-  "working_on",
-  "seconds",
-  "preview_url",
-  "video_url",
-  "studio_url"
-]New value: +[
+  "id",
+  "status",
+  "next",
+  "title",
+  "progress",
+  "working_on",
+  "seconds",
+  "preview_url",
+  "video_url",
+  "studio_url",
+  "image_url"
+]

Changed2 schema fields changedOct 18, 2026

removedOutput schema / properties / image_url

Removed value: -{
-  "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "next",
-  "title",
-  "progress",
-  "working_on",
-  "seconds",
-  "preview_url",
-  "video_url",
-  "studio_url",
-  "image_url"
-]New value: +[
+  "id",
+  "status",
+  "next",
+  "title",
+  "progress",
+  "working_on",
+  "seconds",
+  "preview_url",
+  "video_url",
+  "studio_url"
+]

Changed2 schema fields changedOct 16, 2026

addedOutput schema / properties / image_url

Added value: +{
+  "description": "The character's drawing, as Alpy draws it. Show this, never a picture from elsewhere.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "next",
-  "title",
-  "progress",
-  "working_on",
-  "seconds",
-  "preview_url",
-  "video_url",
-  "studio_url"
-]New value: +[
+  "id",
+  "status",
+  "next",
+  "title",
+  "progress",
+  "working_on",
+  "seconds",
+  "preview_url",
+  "video_url",
+  "studio_url",
+  "image_url"
+]

First observedOct 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower and the description adds real context on top: the returned links expire after an hour, and the call requires an authenticated account or API key. It does not mention rate limits or behavior for unknown/expired ids, so it falls short of a 5.

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?

Two compact sentences, front-loaded with what is returned before the access prerequisite. The phrasing is slightly awkward ('and, once made, links to...') but nothing is wasted.

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?

With an output schema present, return values need not be spelled out, yet the description still anchors the key payload (status, progress, links) and flags link expiry and auth needs. Complete enough for a one-parameter status tool; only the relationship to sibling list/creation tools is unaddressed.

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?

The single id parameter is fully documented in the schema (100% coverage, including the hint that it comes from create_video), so the baseline is 3. The description adds no additional parameter detail and does not need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource and verb-equivalent: it reports 'where a video is', its status and progress, and available links. An agent can tell this apart from create_video/make_full_video from the wording, though it never explicitly names a sibling or contrasts with list_videos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a prerequisite (a connected Alpy account or API key) and implies the post-creation polling flow via 'Says what to do next', but there is no explicit when-to-use versus list_videos or how this fits the create_video -> get_video sequence. Usage is implied rather than stated.

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

All Alpy tools Inspect

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

Need Help?