Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList news

myanimelist_news_list
Read-onlyIdempotent

Fetch MyAnimeList news articles 20 per page and paginate with a cursor to browse updates in sequence.

Instructions

List MyAnimeList news 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_news_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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds the useful behavioral detail of 20 items per page, but says nothing about ordering, freshness, or what fields an article carries; cursor mechanics are already in the schema.

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, front-loaded with purpose and page size. Minor redundancy in restating the cursor paging hint already covered by the schema.

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?

A simple list tool with rich annotations and full schema coverage, so little is required. However, with no output schema the description never characterizes what a news article record contains, leaving that gap 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 the schema documents cursor, context, llm_model, and conversation_id. The description only echoes the cursor parameter and adds no meaning beyond the schema's own wording, so 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+resource: "List MyAnimeList news articles, 20 per page, with a cursor." An agent can tell it apart from myanimelist_news_get by the 'list' framing, though the description never explicitly contrasts them.

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?

Provides a pagination hint (use cursor when paginated) but gives no guidance on when to pick this tool over myanimelist_news_get or the other news siblings. Usage is implied rather than directed.

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