Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList season

myanimelist_season_get
Read-onlyIdempotent

Retrieve every anime title card for a specified MyAnimeList season and year, so you can review a full seasonal lineup in one call.

Instructions

Get a whole MyAnimeList anime season with every title card. Requires year and season.

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": {
      "year": "<year>",
      "season": "<season>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_season_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesRequired. Season year, e.g. `2018`. A season with no titles is still `found` with an empty list; only a year with no season data answers `not_found`.
seasonYesRequired. Season name: `winter`, `spring`, `summer` or `fall`.
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

B3.2/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 contributes only the detail that the response is the whole season with every title card (i.e., an unfiltered, presumably unpaginated listing), which is modest but real added context. It says nothing about rate limits or the not_found/found distinction that the schema mentions.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is largely redundant with the schema's required list, which keeps it from being maximally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with full annotation and schema coverage, the definition is adequate but thin: there is no output schema, and "title card" is never characterized, so the agent cannot anticipate the shape of returned records. It also omits the empty-season versus not_found distinction that matters for interpreting results.

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 all five parameters, including the year bounds and season enum, are already documented in the schema. The description merely echoes that year and season are required and adds no format or interpretation detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: fetch an entire MyAnimeList anime season including all title cards. This is distinguishable from the sibling myanimelist_seasons_list (which presumably enumerates seasons rather than returning a season's titles), though the description never names that alternative explicitly.

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

Usage Guidelines2/5

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

"Requires `year` and `season`" is a parameter requirement restated from the schema, not usage guidance. There is no statement of when to reach for this versus myanimelist_seasons_list or myanimelist_genre_titles_list, and no note on how to handle an unknown/empty season beyond what the schema already says.

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