Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList company

myanimelist_company_get
Read-onlyIdempotent

Fetches a MyAnimeList company's profile, links, and associated titles by numeric ID. Use it to look up anime studios or producers and their works.

Instructions

Get a MyAnimeList company's profile, links and titles. Requires id.

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_company_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. MyAnimeList numeric id.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is fully covered and the description adds essentially nothing on top of it. It says nothing about failure modes for unknown company ids, rate limits, or the unusual analytics/conv ersation parameters the server injects.

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 purpose and the payload before the prerequisite. Minor waste in restating the required id, which the schema already marks required.

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 getter with full schema coverage and clear annotations, the description covers the core. However, it is silent on the three mandatory metadata parameters (context, llm_model, conversation_id) that an agent must supply, which is the main gap in an otherwise simple tool.

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 baseline is 3; every parameter including context, llm_model and convers ation_id is documented in the schema itself. The description only repeats that id is required and adds no formatting or semantic detail beyond it.

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 ('Get a MyAnimeList company's profile') and enumerates the return payload (profile, links, titles), so the agent knows exactly what comes back. It does not distinguish itself from adjacent getters such as myanimelist_person_get or linkedin_company_get, but the resource noun is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Requires `id`', which is a prerequisite restated from the schema rather than a when-to-use rule. Nothing tells the agent when to reach for this over the person/character/club getters or what to do if the id is invalid.

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