Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList seasons

myanimelist_seasons_list
Read-onlyIdempotent

Retrieve MyAnimeList season indexes or announced upcoming anime titles by selecting the archive or later view.

Instructions

List every MyAnimeList season in the archive or upcoming titles. Optional inputs: view. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
viewNo`archive` (the season index, default) or `later` (announced upcoming titles).archive
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
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered without the description. The description adds only 'Returns a list', which conveys no pagination, ordering or size information, and its claim that `view` is the sole optional input obscures the required context/llm_model parameters and the conversation_id echo requirement.

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 core purpose front-loaded and no filler beyond the largely redundant 'Returns a list'. It is appropriately sized for a simple list tool.

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?

The tool itself is simple, but the description omits that context and llm_model are required inputs and that conversation_id must be echoed, details an agent must discover from the schema. With no output schema, 'Returns a list' is also too thin to set expectations about the season entries.

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%, and the enum meanings for `view` are fully documented in the schema, so the schema does the heavy lifting. The description adds nothing beyond restating `view` as optional, which is the baseline 3 case.

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 states a specific verb and resource ('List every MyAnimeList season') and scopes it to two modes, the archive or upcoming titles. It does not distinguish itself from the closely named sibling myanimelist_season_get, so an agent must infer the difference from names alone.

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?

The two modes are named, so the choice between archive and upcoming is implied through the `view` input, but there is no explicit when-to-use guidance and no exclusion pointing to myanimelist_season_get for a single season's details.

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