Skip to main content
Glama
Grinv

MAL MCP Server

Get producers/studios

get_producers
Read-only

Search and browse anime producers and studios with MAL IDs, anime counts, and pagination. Filter by name or letter, sort results, and find studios for detailed profile lookups.

Instructions

List or search anime producers and studios with their MAL IDs and counts. Use q to search by name, then get_producer for one studio's full profile (about text, external links).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFilter by name.
pageNo1-based page number for pagination (1-1000).
sortNoSort direction.
limitNoMax results per page (1-50).
letterNoRestrict results to entries whose title starts with this single letter.
order_byNoField to order by.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed27 schema fields changedv0.9.0
    • addedInput schema / properties / letter
      Added value: +{
      +  "description": "Restrict results to entries whose title starts with this single letter.",
      +  "maxLength": 1,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per page (1-25)."New value: +"Max results per page (1-50)."
    • changedInput schema / properties / limit / maximum
      Previous value: -25New value: +50
    • changedInput schema / properties / page / description
      Previous value: -"1-based page number for pagination."New value: +"1-based page number for pagination (1-1000)."
    • changedInput schema / properties / page / maximum
      Previous value: -9007199254740991New value: +1000
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "desc",
      -  "asc"
      -]New value: +[
      +  "asc",
      +  "desc"
      +]
    • addedOutput schema / properties / page / properties / current_page / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / page / properties / current_page / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / page / properties / current_page / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / page / properties / last_visible_page / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / page / properties / last_visible_page / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / page / properties / last_visible_page / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / page / properties / total / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / page / properties / total / minimum
      Added value: +0
    • changedOutput schema / properties / page / properties / total / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / results / items / properties / count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / results / items / properties / count / minimum
      Added value: +0
    • changedOutput schema / properties / results / items / properties / count / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / results / items / properties / established / format
      Added value: +"date-time"
    • addedOutput schema / properties / results / items / properties / established / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • addedOutput schema / properties / results / items / properties / favorites / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / results / items / properties / favorites / minimum
      Added value: +0
    • changedOutput schema / properties / results / items / properties / favorites / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / results / items / properties / mal_id / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / results / items / properties / mal_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / results / items / properties / mal_id / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / results / items / required
      Added value: +[
      +  "mal_id"
      +]
  2. Changed1 schema field changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. 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": {
      +    "page": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "current_page": {
      +          "type": "number"
      +        },
      +        "has_next_page": {
      +          "type": "boolean"
      +        },
      +        "last_visible_page": {
      +          "type": "number"
      +        },
      +        "total": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "count": {
      +            "type": "number"
      +          },
      +          "established": {
      +            "type": "string"
      +          },
      +          "favorites": {
      +            "type": "number"
      +          },
      +          "image_url": {
      +            "type": "string"
      +          },
      +          "mal_id": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "page"
      +  ],
      +  "type": "object"
      +}
  4. Addedv0.2.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare 'readOnlyHint: true' and 'openWorldHint: true', so the description does not need to reiterate safety. It adds context about returning MAL IDs and counts, but does not elaborate on pagination, sorting behavior, or other relevant details. With annotations present, a score of 3 is appropriate – adequate but not exemplary.

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 two sentences long, front-loaded with the core purpose, and wastes no words. Every sentence adds value: the first defines the tool, the second gives usage guidance and references the sibling tool for further action.

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?

Given that an output schema exists (so return values are documented elsewhere) and annotations declare read-only and open-world behavior, the description is complete enough for an agent to correctly invoke the tool. It covers the primary use case, search, and directs to the sibling tool for deeper details.

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 coverage is 100%, so the description adds no additional meaning beyond what the schema provides. The description notes the 'q' parameter for search, but the schema already describes it as 'Filter by name.' No extra semantic value is provided for other parameters. Baseline 3 is correct.

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 clearly states the action ('List or search') and the resource ('anime producers and studios'), and explicitly mentions the output includes 'MAL IDs and counts'. It distinguishes from the sibling tool 'get_producer' by referencing it as a different tool for full profiles.

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 explicitly states when to use this tool ('Use `q` to search by name') and provides a clear alternative ('then get_producer for one studio's full profile'). This helps the agent know when to choose this tool over the sibling 'get_producer'.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/mal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server