Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList suggestions

myanimelist_suggest
Read-onlyIdempotent

Fetches MyAnimeList autocomplete suggestions for anime, manga, characters, people, and other categories, helping users find the right title or entity from a partial query.

Instructions

Get MyAnimeList autocomplete suggestions across anime, manga, characters, people and more. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoCategory to autocomplete: anime, manga, character, person, user, company, club, news, featured, forum, or all.all
queryYesRequired. Autocomplete text.
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
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. Beyond that the description offers only 'Returns a list', which says nothing about the shape of a suggestion, the effect of the `kind` filter, or the conversation_id sequencing requirement. It adds almost no behavioral context on top of the 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 with the resource and scope front-loaded and no filler. Minor waste: 'Requires `query`' duplicates the schema's required list, and 'Returns a list' is close to a tautology for a suggest endpoint.

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?

There is no output schema, so the description is the only place return values could be characterized, and 'Returns a list' does not say what a suggestion contains (id, title, image, type). The five-parameter surface, including the analytics and conversation_id fields, is fully documented in the schema, so the gap is confined to return semantics.

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%, with `kind` enumerating all eleven categories and each analytics parameter explained in-schema. The description only restates that `query` is required, which the schema already marks as required. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Get MyAnimeList autocomplete suggestions across anime, manga, characters, people and more.' That distinguishes it reasonably from the *_list and *_get siblings, which return full entities rather than autocomplete matches. It stops short of naming a sibling alternative, but the purpose is unmistakable.

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 word 'autocomplete' implies typeahead/search-as-you-type usage, and the 'Requires `query`' clause signals it is a lookup keyed on partial text. However, there is no explicit when-to-use or when-not-to-use guidance and no pointer to a sibling for full-record retrieval (e.g. myanimelist_anime_get). Usage is inferable but not stated.

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