AnimeAPI

Get anime video

get_anime_video

Read-onlyIdempotent

Check on a video started with generate_anime_video. Returns its status (processing, succeeded or failed) and, once succeeded, the MP4 URL. Free. If it is still processing, wait a minute and call again.

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": {
      "id": "<id>"
    },
    "name": "get_anime_video"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The video id returned by generate_anime_video.

Output Schema

Name	Required	Description	Default
`id`	Yes
`error`	Yes
`prompt`	Yes
`status`	Yes
`cost_usd`	Yes
`duration`	Yes
`refunded`	Yes
`video_url`	Yes
`created_at`	Yes
`last_frame`	Yes
`resolution`	Yes
`balance_usd`	No
`first_frame`	Yes
`orientation`	Yes
`enhanced_prompt`	Yes
`generation_time_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuinely new behavioral context: the tool is free, the three possible status outcomes, that the MP4 URL only appears after success, and the recommended polling interval. Only the absence of guidance on failure handling or how long a job typically takes keeps this from 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.

Conciseness5/5

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

Four short sentences, no filler: what it does, what it returns, cost, and the polling loop. The identifying purpose is front-loaded and every sentence carries information the agent needs.

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?

With an output schema present, the description need not restate the response shape, and it still summarizes the meaningful fields (status, MP4 URL). Combined with the polling instruction, an agent has everything needed to call and re-call this tool correctly.

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?

There is one required parameter with 100% schema coverage, and the schema already explains that the id comes from generate_anime_video. The description reinforces that provenance but adds no format, length, or validity details beyond the schema, so the baseline of 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 ("Check on a video") and immediately ties it to its companion tool "generate_anime_video", which is exactly the sibling an agent would confuse it with. The description also enumerates the returned status values, so the agent knows precisely what this tool produces.

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?

Gives a clear precondition (only for a video started with generate_anime_video) and explicit operational guidance: "If it is still processing, wait a minute and call again." That is actionable polling advice. It stops short of a full when-not statement, but the prerequisite framing makes the boundary unambiguous.

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

All AnimeAPI tools Inspect

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

Need Help?