MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get manga magazines

get_magazines

Read-only

Search manga magazines or publishers by name, letter, or sort criteria, and retrieve MAL IDs with manga counts for use in manga search filters.

Instructions

List or search manga serialization magazines/publishers (e.g. Weekly Shonen Jump) with their MAL IDs and manga counts. Use q to search by name, or look up an ID here for search_manga's magazines filter.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Filter by name.
`page`	No	1-based page number for pagination (1-1000).
`sort`	No	Sort direction.
`limit`	No	Max results per page (1-100).
`letter`	No	Restrict results to entries whose title starts with this single letter.
`order_by`	No	Field to order by.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Jul 30, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already indicate read-only and open-world behavior. Description adds the returned fields (MAL IDs, manga counts) but no additional behavioral detail.

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?

Two efficient sentences: first states function and output, second gives usage guidance. No wasted words.

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 output schema present, description covers core data, pagination implied, and explains integration with search_manga—complete for a listing tool.

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 provides full parameter descriptions. The description adds value by explaining the 'q' parameter's purpose and tying output to search_manga usage.

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?

Description clearly states the tool lists/seraches magazines with MAL IDs and manga counts, distinguishing it from sibling tools like search_manga which uses the ID as a filter.

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 advises using 'q' for name search and looking up IDs for search_manga's filter. Lacks explicit when-not-to-use but provides clear usage context.

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

Deploy Server