Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList featured articles

myanimelist_featured_list
Read-onlyIdempotent

Fetches MyAnimeList featured articles in pages of 20 and accepts a cursor to retrieve subsequent pages, helping you browse or aggregate featured content.

Instructions

List MyAnimeList featured articles, 20 per page, with a cursor. Optional inputs: cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_featured_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/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 covered. The description adds genuine value by disclosing the fixed 20-per-page batching and that results are cursor-paginated, but says nothing about ordering, staleness, or what an article record contains.

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

Conciseness3/5

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

The description is short and front-loads the resource, which is good. However, the cursor concept is repeated three times ("with a cursor," "Optional inputs: `cursor`," "use cursor when paginated"), which is redundant for a single-sentence 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?

For a simple paginated list tool with no output schema, the description is minimally adequate: it conveys page size and pagination mechanics. It leaves gaps on what an article object looks like and on termination conditions for the cursor loop, which matter given there is no output schema to consult.

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 four parameters (including cursor, context, llm_model, conversation_id) are already documented in the schema. The description's mention of `cursor` adds nothing beyond the schema's own instruction to pass page.nextCursor, so the baseline of 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?

States a specific verb and resource ("List MyAnimeList featured articles") plus the page size, so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling myanimelist_featured_get, which an agent would have to infer from the List/Get naming.

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 only guidance is "use cursor when paginated," which implies the pagination workflow but never states when to pick this tool over featured_get or the other *_list siblings. Usage is implied rather than explained.

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