Skip to main content
Glama

AnimeAPI

Generate anime video

generate_anime_video

Generate one anime-style video clip (MP4, 24 fps, with sound) from a text prompt, optionally starting and/or ending on given images. Priced per second of video, charged up front and refunded on failure: 480p $0.016/s, 768p $0.04/s (a 5s 768p clip is $0.20, 15s is $0.60). Ask the user before long or repeated videos. Waits for the render for a few minutes; if it isn't done by then, returns the video id to pass to get_anime_video.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_anime_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesWhat happens in the clip, in plain English: subject, action, camera, mood. An anime style is added automatically.
durationNoLength in seconds. The price is per second.
resolutionNo768p
orientationNo9:16, 1:1 or 16:9. Ignored when first_frame_url is set: the image sets the shape.landscape
last_frame_urlNoPublic image URL the clip ends on.
first_frame_urlNoPublic image URL the clip starts on (image-to-video).

Output Schema

NameRequiredDescriptionDefault
idYes
errorYes
promptYes
statusYes
cost_usdYes
durationYes
refundedYes
video_urlYes
created_atYes
last_frameYes
resolutionYes
balance_usdNo
first_frameYes
orientationYes
enhanced_promptYes
generation_time_msYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses pricing per second and resolution, upfront charging with refund on failure, render wait behavior, and the fallback of returning a video id. This is meaningful operational context for a costly, non-idempotent generation tool.

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?

The description is front-loaded with what is generated, then cost, then wait/fallback behavior. Every sentence contributes useful decision information, and the parenthetical price examples are compact.

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 a generation tool with six parameters, an output schema, and annotations covering openness and idempotency, the description supplies the missing decision-critical details: cost, confirmation guidance, wait behavior, and fallback retrieval. Nothing an agent needs in order to call it correctly appears absent.

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 coverage is high, so the baseline is 3, but the description adds pricing semantics that map resolution and duration to concrete cost, and clarifies that first/last frame images are optional starting/ending anchors. It does not restate enum meanings such as orientation, which the schema already handles.

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 verb and resource ('Generate one anime-style video clip') plus concrete output traits (MP4, 24 fps, sound) and optional start/end images. It also distinguishes the retrieval sibling by saying the video id should be passed to get_anime_video.

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?

It gives clear cost-related guidance ('Ask the user before long or repeated videos') and explains the wait/fallback path to get_anime_video. It does not explicitly contrast with generate_anime_image, but the context signals do not require inferring unstated alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources