Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList rankings

myanimelist_top_list
Read-onlyIdempotent

Fetch MyAnimeList anime or manga rankings, 50 rows per page. Filter by type such as airing, upcoming, or bypopularity, and use the cursor to page through results.

Instructions

List MyAnimeList anime or manga rankings, 50 rows per page. Requires kind. 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": {
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_top_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesRequired. `anime` or `manga`.
typeNoRanking type; omit for the overall ranking of the kind.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two useful behavioral facts beyond that: a fixed page size of 50 rows and that pagination is cursor-driven. It does not mention rate limits, upstream API constraints, or what happens at the end of the ranking.

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?

A single front-loaded sentence that leads with the action and resource, then appends page size and cursor handling. 'Returns a list' is mildly redundant, but nothing else is wasted.

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 six-parameter tool with three required params (context, llm_model, conversation_id) and no output schema, the description says nothing about the pagination contract's return shape or the ranking type options. It is adequate only because the input schema is fully documented; an agent must read the schema to learn the rest.

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%, including enum documentation for kind and type and cursor semantics, so the schema does the heavy lifting. The description restates 'Requires kind' and the cursor usage rule, adding little beyond what is already structured; 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?

Specific verb plus resource ('List MyAnimeList anime or manga rankings') with the domain split named explicitly. It is distinguishable from siblings like myanimelist_genre_titles_list or myanimelist_featured_list by the 'rankings' framing, though it never names an alternative to sharpen that boundary.

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?

The description gives no when-to-use or when-not-to-use guidance relative to the many sibling list tools (genre titles, featured, seasonal, user lists). The only procedural hint is 'use cursor when paginated', which is parameter mechanics rather than tool selection guidance.

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