Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList user activity

myanimelist_user_activity_list
Read-onlyIdempotent

Fetch a public MyAnimeList user's anime, episode, or manga activity by username to review their recent updates.

Instructions

List a public MyAnimeList user's anime, episode or manga activity. Requires username. 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": {
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_user_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKind: `anime` (list updates), `episode` (episode updates) or `manga`.anime
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Public MyAnimeList member name, e.g. `TheLlama`.
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, openWorld, idempotent and non-destructive, so the safety profile is covered. The description's one added fact is the 'public user' access constraint, plus a terse 'Returns a list' that gives no shape; there is nothing on result ordering, result caps, or empty-activity behavior.

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, front-loaded with the core action and no filler. 'Requires `username`. Returns a list.' partly repeats what the schema already marks as required, so it is efficient but not free of redundancy.

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 list with rich annotations, full schema coverage and no output schema, the essentials are present. Missing are any mention of pagination, result limits, or how activity entries are ordered, which an agent would need to page or interpret results correctly.

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 enum for `kind` and the `username` pattern are fully documented in the input schema already. The description adds no format, default, or filtering semantics beyond restating that `username` is required and that activity can be anime, episode or manga.

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?

A specific verb plus resource: 'List a public MyAnimeList user's anime, episode or manga activity', with the three activity kinds enumerated. An agent can tell it is an activity-feed read rather than a catalogue lookup, though it never names the nearest sibling (myanimelist_user_anime_list_list) to say how the two differ.

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 requirement of a public profile and the `kind` selector imply when the tool applies, but there is no explicit when-to-use/when-not guidance and no pointer to the user-list, reviews, or statistics siblings for adjacent needs. Usage must be inferred from the schema rather than the prose.

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