Skip to main content
Glama

openart_get_video_status

Read-only

Retrieve the rendering status and URL for an OpenArt video by providing its ID.

Instructions

Check the rendering status and URL of an OpenArt video by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYes

Implementation Reference

  • The actual handler function `getVideoStatus` that checks rendering status and URL of an OpenArt video by ID. Navigates to the video page, scrapes status, video URL, thumbnail, and prompt from DOM.
    export async function getVideoStatus(videoId: string): Promise<Video> {
      const page = await newPage();
      try {
        await page.goto(`${BASE_URL}/video/${videoId}`);
        await page.waitForLoadState("networkidle");
    
        // TODO: real selectors.
        const status = (await page.locator('[data-video-status]').getAttribute("data-status")) as Video["status"];
        const videoUrl = await page.locator("video source").first().getAttribute("src");
        const thumb = await page.locator('[data-video-thumbnail]').getAttribute("src");
        const prompt = (await page.locator('[data-video-prompt]').textContent())?.trim();
    
        return {
          id: videoId,
          status: status || "rendering",
          url: videoUrl || undefined,
          thumbnail_url: thumb || undefined,
          prompt,
        };
      } finally {
        await page.close();
      }
    }
  • The `Video` interface type definition used as the return type of `getVideoStatus`. Defines fields: id, status (queued/rendering/complete/failed), url, thumbnail_url, prompt.
    export interface Video {
      id: string;
      status: "queued" | "rendering" | "complete" | "failed";
      url?: string;
      thumbnail_url?: string;
      prompt?: string;
    }
  • src/index.ts:70-79 (registration)
    Tool registration in the tools array: defines name 'openart_get_video_status', description, inputSchema (video_id required string), and annotations.
    {
      name: "openart_get_video_status",
      description: "Check the rendering status and URL of an OpenArt video by ID.",
      inputSchema: {
        type: "object",
        properties: { video_id: { type: "string" } },
        required: ["video_id"],
      },
      annotations: { readOnlyHint: true, openWorldHint: true },
    },
  • src/index.ts:115-117 (registration)
    Tool handler dispatch in the CallToolRequestSchema switch statement: maps 'openart_get_video_status' to call `getVideoStatus` with the parsed video_id argument.
    case "openart_get_video_status":
      result = await getVideoStatus(z.object({ video_id: z.string() }).parse(args).video_id);
      break;
  • src/index.ts:14-16 (registration)
    Import of the `getVideoStatus` function from ./tools.js at the top of index.ts.
      getVideoStatus,
      cleanup,
    } from "./tools.js";
Behavior2/5

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

Annotations indicate readOnlyHint and openWorldHint, but description adds no behavioral traits beyond the obvious. No mention of rate limits, response format, or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, zero waste, perfectly front-loaded with the core action and object.

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 simple status-check tool with one parameter and annotations present, the description is adequate but lacks mention of output format or error handling.

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

Parameters2/5

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

Schema coverage is 0%, and description does not explain the 'video_id' parameter (e.g., format, length, source). A simple parameter but additional context would help.

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 the verb 'check' and the resource 'rendering status and URL of an OpenArt video', and distinguishes from sibling tools focused on characters and video generation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives, nor any context on prerequisites or exclusions. Sibling tools exist but no differentiation is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbertus/openart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server