Skip to main content
Glama
Sign In
MAL MCP Server

MAL MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get manga genres

get_manga_genres
Read-only

Retrieve manga genres, themes, and demographics with their MAL IDs so you can build valid genre filters for manga searches. Optionally exclude adult or Ecchi tags.

Instructions

List manga genres/themes/demographics with their MAL IDs. Use this to discover the numeric IDs that the genres parameter of search_manga expects. sfw/sfw_strict drop the adult (and, for sfw_strict, Ecchi) genres from the list itself.

Input Schema

NameRequiredDescriptionDefault
sfwNoIf true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.
filterNoRestrict to one kind of tag. Omit to list all.
sfw_strictNoIf true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.

Output Schema

NameRequiredDescriptionDefault
genresYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • addedInput schema / properties / sfw
      Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sfw_strict
      Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.",
+  "type": "boolean"
+}
  2. Changed7 schema fields changedv0.9.0
    • addedOutput schema / properties / genres / items / properties / count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / genres / items / properties / count / minimum
      Added value: +0
    • changedOutput schema / properties / genres / items / properties / count / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / genres / items / properties / mal_id / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / genres / items / properties / mal_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / genres / items / properties / mal_id / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / genres / items / required
      Added value: +[
+  "mal_id"
+]
  3. Changed1 schema field changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed2 schema fields changedv0.7.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "genres": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "mal_id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "genres"
+  ],
+  "type": "object"
+}
  5. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description goes further by disclosing that sfw/sfw_strict remove genres from the returned list itself and that sfw_strict additionally drops Ecchi — an effect on output content, not just on filtering, which is real added context.

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 short sentences: purpose, downstream use, and filter side-effect — ordered by importance with zero filler. Nothing needs trimming and nothing is buried.

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 available and full parameter documentation, the description needn't explain return shapes. It covers purpose, routing, and filter consequences; the only minor omission is any mention of the `filter` parameter's role, which the schema handles well.

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%, including the sfw/sfw_strict distinction and the filter enum, so the schema does the heavy lifting. The description's restatement of the sfw behavior is a useful summary but adds no syntax or format detail beyond the schema, so baseline 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 (list manga genres/themes/demographics) plus what the output carries (MAL IDs). The 'manga' qualifier cleanly separates it from the sibling get_anime_genres without either schema being opened.

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?

Explicitly routes the agent: use this to obtain numeric IDs that search_manga's `genres` parameter expects, naming the consuming sibling. It stops short of stating when not to use it (e.g. versus get_anime_genres), but the manga scoping makes the alternative obvious.

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