Skip to main content
Glama

get_thread

Retrieve a specific thread from AniList by its unique ID using the dedicated API tool for streamlined data access.

Instructions

Get a specific thread by its AniList ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe AniList ID of the thread

Implementation Reference

  • Handler function that retrieves a specific AniList thread by ID using anilist.thread.get(id), returns the thread as JSON string, or an error message if failed.
    async ({ id }) => {
      try {
        const thread = await anilist.thread.get(id);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(thread, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema defining the required 'id' parameter as a number with description.
    {
      id: z.number().describe("The AniList ID of the thread"),
    },
  • tools/thread.ts:55-83 (registration)
    Registration of the 'get_thread' tool on the MCP server, including name, description, input schema, metadata hints, and handler reference.
      "get_thread",
      "Get a specific thread by its AniList ID",
      {
        id: z.number().describe("The AniList ID of the thread"),
      },
      {
        title: "Get AniList Thread",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ id }) => {
        try {
          const thread = await anilist.thread.get(id);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(thread, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions retrieval by ID but doesn't specify if this is a read-only operation, what permissions are needed, error handling for invalid IDs, or the format of the returned thread. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly communicates the tool's function in a compact form, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what a 'thread' entails in this context, what data is returned, or any behavioral aspects like rate limits or authentication needs. Given the lack of structured data, more contextual information is needed for effective use.

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 the single parameter 'id' documented as 'The AniList ID of the thread'. The description adds no additional parameter semantics beyond what the schema provides, such as ID format examples or validation rules. Baseline 3 is appropriate given the schema handles parameter documentation adequately.

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 clearly states the action ('Get') and resource ('a specific thread'), specifying it's retrieved by 'AniList ID'. It distinguishes from siblings like 'get_thread_comments' by focusing on thread retrieval rather than comments, but doesn't explicitly contrast with all other 'get_' tools. The purpose is specific and 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 description provides no guidance on when to use this tool versus alternatives like 'search_activity' or 'get_activity' for finding threads, nor does it mention prerequisites or context for usage. It simply states what the tool does without indicating appropriate scenarios or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuna0x0/anilist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server