Skip to main content
Glama
junmer

LottieFiles MCP Server

search_animations

Find Lottie animations using keywords or tags. Supports pagination to browse results efficiently.

Instructions

Search for Lottie animations by keywords, tags, and other criteria. Supports pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch keywords that match animation names, descriptions, tags, etc.
pageNoPage number, starting from 1
limitNoNumber of items per page

Implementation Reference

  • Executes the 'search_animations' tool by calling LottieApiClient.searchAnimations and returning the results as a JSON string in the MCP response format.
    case "search_animations":
      const list = await this.apiClient.searchAnimations(
        args?.query as string,
        args?.page as number,
        args?.limit as number
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                count: list.length,
                animations: list,
              },
              null,
              2
            ),
          },
        ],
      };
  • Performs the actual API call to LottieFiles search endpoint to retrieve animations matching the query.
    async searchAnimations(query: string, page: number = 1, limit: number = 20) {
      try {
        const response = await this.axiosInstance.get(
          `${this.baseUrl}/search/get-animations`,
          {
            params: {
              query,
              page,
              limit,
            },
          }
        );
        return response.data.data.data;
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to search animations: ${error.message}`);
        }
        throw new Error("Failed to search animations: Unknown error");
      }
  • Registers the 'search_animations' tool in the MCP listTools response, defining its name, description, and input schema.
    {
      name: "search_animations",
      description:
        "Search for Lottie animations by keywords, tags, and other criteria. Supports pagination.",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description:
              "Search keywords that match animation names, descriptions, tags, etc.",
          },
          page: {
            type: "integer",
            description: "Page number, starting from 1",
            minimum: 1,
            default: 1,
          },
          limit: {
            type: "integer",
            description: "Number of items per page",
            minimum: 1,
            maximum: 100,
            default: 20,
          },
        },
      },
    },
  • TypeScript interface defining the input parameters for search_animations.
    export interface SearchAnimationsParams {
      query: string;
      page?: number;
      limit?: number;
    }
  • TypeScript interface defining the expected response structure for search_animations.
    export interface SearchAnimationsResponse {
      animations: LottieAnimation[];
      total: number;
      page: number;
      limit: number;
    }
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. It mentions 'Supports pagination', which adds some behavioral context beyond the input schema. However, it lacks details on authentication needs, rate limits, error handling, or what the search results look like (e.g., format, fields). For a search tool with zero annotation coverage, this is insufficient.

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 two concise sentences with zero waste: the first states the purpose and criteria, the second adds pagination support. It's front-loaded and appropriately sized, with every sentence earning its place.

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?

Given no annotations, no output schema, and a search tool with 3 parameters, the description is incomplete. It doesn't explain what the search returns (e.g., list of animations with IDs/names), potential constraints like rate limits, or how to handle errors. This leaves significant gaps for an agent to use the tool effectively.

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 clear docs for 'query', 'page', and 'limit'. The description adds minimal value by mentioning 'keywords, tags, and other criteria' which loosely relates to the 'query' parameter, but doesn't provide additional syntax or format details. Baseline 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: 'Search for Lottie animations by keywords, tags, and other criteria.' It specifies the verb ('Search') and resource ('Lottie animations'), but doesn't explicitly differentiate from siblings like 'get_popular_animations' which might retrieve animations without search criteria. This makes it clear but not fully sibling-aware.

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 'get_animation_details'. It mentions 'Supports pagination' which hints at usage for large result sets, but lacks explicit when/when-not scenarios or prerequisites, leaving the agent to infer context.

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