Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search MyAnimeList

myanimelist_search
Read-onlyIdempotent

Search MyAnimeList for anime, manga, characters, or people by query and return paginated matches.

Instructions

Search MyAnimeList anime, manga, characters and people. Requires query. Returns a list (use cursor when paginated).

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat to search: `anime`, `manga`, `character` or `person`. Defaults to `anime`.anime
queryYesRequired. Search text. At least three characters, or one or more Chinese or Japanese characters.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a modest amount beyond that: it says results come back as a list and that cursor-based pagination exists. It says nothing about result ordering, relevance ranking, or result volume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the resource scope front-loaded and no filler. The 'Requires `query`' clause mildly duplicates the schema's own required/description fields, which keeps it from a perfect score.

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?

For a simple search tool with full schema coverage, complete annotations and no output schema, the definition covers scope, the required input and pagination adequately. The only gap is routing guidance relative to the many sibling retrieval tools, which the description leaves unaddressed.

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%, so every parameter including kind, query, cursor, context, llm_model and conversation_id is already documented in the schema. The description merely restates that `query` is required and cursor drives pagination, adding no syntax or format meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Search) and resource (MyAnimeList anime, manga, characters and people), and the kind enum reinforces the four searchable domains. It is clear what the tool does, but it never distinguishes itself from retrieval siblings such as myanimelist_anime_get or myanimelist_top_list, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the text states `query` is required and that a cursor should be used when paginated, which tells an agent how to call it but not when to prefer it over a specific-title get or a genre/top listing tool. There are no explicit exclusions or named alternatives.

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