Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get anime videos

get_anime_videos
Read-only

Get every promotional video for an anime: trailers, episode previews, and openings/endings. Returns title, watch URL, thumbnail, and view/like counts. Enter the anime's MAL ID.

Instructions

List an anime's promotional videos (PVs/trailers), episode preview clips, and music videos (openings/endings), each with a title, watch URL, thumbnail, and view/like counts where available. This is richer than get_anime's single trailer field — use this instead when the caller wants every promo, not just the main one. Get the mal_id from search_anime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMyAnimeList numeric ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
promoYes
episodesYes
music_videosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • addedOutput schema / properties / music_videos / items / properties / comment_count
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / music_videos / items / properties / duration
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / music_videos / items / properties / published_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / promo / items / properties / comment_count
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / promo / items / properties / duration
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / promo / items / properties / published_at
      Added value: +{
+  "type": "string"
+}
  2. Addedv0.9.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description does not contradict this. Beyond that, the description discloses the scope of results (multiple video categories), the per-item attributes returned, and the 'where available' caveat for count data. It does not discuss rate limits or authentication, but those are less critical for a read-only, single-ID lookup with a full output schema.

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?

Three sentences with no filler. The first sentence front-loads the core action and scope, the second differentiates from a sibling, and the third gives a necessary prerequisite. Every sentence earns its place.

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 one trivial parameter, a full input schema, an output schema, and read-only annotations, the description is complete for an agent to select and invoke the tool correctly. It even provides the upstream workflow for obtaining the required ID.

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%, and the schema already documents id as a MyAnimeList numeric ID with bounds. The description adds the practical instruction to fetch that ID from search_anime, which is useful, but it does not need to restate parameter details already covered by the schema. Baseline 3 is appropriate.

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 names a specific verb ('List'), a specific resource ('an anime's promotional videos'), and enumerates concrete content types: PVs/trailers, episode preview clips, and music videos. It also explicitly contrasts itself with get_anime's single trailer field, so an agent can distinguish this tool from its closest sibling without opening either schema.

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?

The description states when to prefer this tool: when the caller wants every promo rather than just the main one. It also directs the agent to search_anime to obtain the required mal_id, which is a direct prerequisite for invoking the tool correctly.

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

Deploy Server

Other Tools