Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get public MyAnimeList profile

myanimelist_user_get
Read-onlyIdempotent

Fetch a public MyAnimeList profile by username to view statistics, favorites, and recent activity. Use it to gather anime and manga user data for social analysis.

Instructions

Get a public MyAnimeList profile with statistics, favourites and activity. Requires username.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered externally. The description adds that only public profiles are returned, but says nothing about behavior for private/nonexistent usernames, rate limiting, or pagination of activity data. Modest added value beyond annotations.

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 the action and return content. The trailing 'Requires `username`' is largely redundant with the schema's own 'Required.' note, keeping it from a perfect score, 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?

With no output schema, the description partly compensates by naming the returned sections (statistics, favourites, activity). However, for a tool with three required parameters including a conversation_id handshake requirement, it offers no guidance on the call-sequence constraint stated in the schema. Adequate but thin for a read tool whose response shape is otherwise unspecified.

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 username parameter already documents its pattern and an example, so the baseline of 3 applies. The description's only parameter remark ('Requires `username`') merely restates requiredness already encoded in the schema. No meaning is added for the auxiliary context, llm_model, or conversation_id parameters.

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: 'Get a public MyAnimeList profile with statistics, favourites and activity.' It also enumerates what the profile payload contains, which distinguishes it from list-oriented siblings like myanimelist_user_anime_list_list and myanimelist_user_activity_list. It stops short of explicitly naming those siblings as alternatives.

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 description states a prerequisite ('Requires `username`') and the 'public' qualifier hints at scope, but it never says when to choose this tool over myanimelist_user_anime_list_list, myanimelist_user_activity_list, or myanimelist_user_reviews_list. Usage must be inferred from the name.

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