Skip to main content
Glama
junmer

LottieFiles MCP Server

get_animation_details

Retrieve comprehensive data about a Lottie animation, including animation details, preview images, and associated tags, by providing its unique identifier.

Instructions

Get detailed information about a specific Lottie animation, including animation data, preview images, and tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier of the animation

Implementation Reference

  • Registration of the 'get_animation_details' tool in the listTools method, including its name, description, and input schema.
    {
      name: "get_animation_details",
      description:
        "Get detailed information about a specific Lottie animation, including animation data, preview images, and tags.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Unique identifier of the animation",
          },
        },
        required: ["id"],
      },
    },
  • The handler case in callTool that executes the get_animation_details tool by calling the API client and returning the details as JSON.
    case "get_animation_details":
      const details = await this.apiClient.getAnimationById(
        args?.id as string
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(details, null, 2),
          },
        ],
      };
  • Core helper method in LottieApiClient that fetches animation details from the LottieFiles API using the provided animation ID.
    async getAnimationById(id: string) {
      try {
        const response = await this.axiosInstance.get(
          `${this.baseUrl}/animations/get-animation-data`,
          {
            params: {
              fileId: id,
            },
          }
        );
    
        return response.data;
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to get animation: ${error.message}`);
        }
        throw new Error("Failed to get animation: Unknown error");
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, or details the return format (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, well-structured sentence that efficiently conveys the tool's purpose and scope without unnecessary words. It is front-loaded with the core action and includes relevant details (animation data, preview images, tags), making it highly concise and effective.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral traits, or output format. Without annotations or an output schema, more guidance would be beneficial, but it meets the minimum for a simple lookup 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?

The input schema has 100% description coverage, with the 'id' parameter clearly documented as a 'Unique identifier of the animation'. The description adds no additional meaning beyond this, such as format examples or sourcing hints. With high schema coverage, the baseline score of 3 is appropriate as 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 clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific Lottie animation'), including what information is retrieved (animation data, preview images, tags). It doesn't explicitly differentiate from siblings like 'get_popular_animations' or 'search_animations', but the focus on a 'specific' animation implies it's for individual lookup rather than listing or searching.

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 'get_popular_animations' or 'search_animations'. It mentions a 'specific' animation, which hints at usage for known IDs, but lacks explicit when/when-not instructions or prerequisites, such as needing an animation ID from another source.

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

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/junmer/mcp-server-lottiefiles'

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