Skip to main content
Glama

get_activity

Retrieve a specific AniList activity by its unique ID using the anilist-mcp server. Input the activity ID to fetch detailed activity data directly from the AniList API.

Instructions

Get a specific AniList activity by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityIDYesThe AniList activity ID

Implementation Reference

  • The handler function for the 'get_activity' tool. It retrieves the specific AniList activity by ID using the anilist library and returns the JSON stringified result or an error message.
    async ({ activityID }) => {
      try {
        const activity = await anilist.activity.get(activityID);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(activity, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Input schema for the 'get_activity' tool, defining the required 'activityID' parameter as a number.
    {
      activityID: z.number().describe("The AniList activity ID"),
    },
  • Registration of the 'get_activity' tool within the registerActivityTools function using McpServer.tool method, including name, description, input schema, metadata, and handler.
    server.tool(
      "get_activity",
      "Get a specific AniList activity by its ID",
      {
        activityID: z.number().describe("The AniList activity ID"),
      },
      {
        title: "Get an AniList Activity",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async ({ activityID }) => {
        try {
          const activity = await anilist.activity.get(activityID);
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(activity, 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 the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, error handling, or response format, which are critical for safe invocation.

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 ('Get a specific AniList activity by its ID') with no wasted words. It's appropriately sized for a simple lookup tool.

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 operation with one parameter and no output schema, the description is minimally adequate but lacks completeness. It doesn't address behavioral aspects like authentication or response structure, which are important given the absence of annotations and output schema, leaving gaps in contextual understanding.

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?

The input schema has 100% description coverage, with the parameter 'activityID' documented as 'The AniList activity ID'. The description adds no additional semantic context beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 verb ('Get') and resource ('a specific AniList activity by its ID'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_user_activity' or 'search_activity', which also retrieve activities but with different scopes or methods.

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. It doesn't mention sibling tools like 'get_user_activity' (for user-specific activities) or 'search_activity' (for broader searches), leaving the agent without context for tool selection.

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