Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

delete-index

Remove a Meilisearch index by its unique identifier to manage search data and free storage space.

Instructions

Delete a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index to delete

Implementation Reference

  • The handler function that performs the actual deletion of the Meilisearch index via the API client, handles errors, and returns the response.
    async ({ indexUid }: DeleteIndexParams) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}`);
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema defining the required 'indexUid' parameter for the delete-index tool.
    {
      indexUid: z.string().describe('Unique identifier of the index to delete'),
    },
  • Registers the 'delete-index' tool with the MCP server using server.tool(), including name, description, schema, and handler function.
    server.tool(
      'delete-index',
      'Delete a Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index to delete'),
      },
      async ({ indexUid }: DeleteIndexParams) => {
        try {
          const response = await apiClient.delete(`/indexes/${indexUid}`);
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:64-64 (registration)
    Top-level call to register all index management tools (including delete-index) to the main MCP server instance.
    registerIndexTools(server);
  • TypeScript interface defining the parameters for the delete-index tool handler.
    interface DeleteIndexParams {
      indexUid: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behavioral traits: whether deletion is permanent, requires specific permissions, affects associated data, or has rate limits. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero waste. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place without redundancy or fluff.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like irreversibility, error conditions, or response format. For a tool that permanently removes data, more context is needed to guide safe usage.

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 'indexUid' well-documented in the schema. The description adds no additional parameter semantics beyond implying the target is a Meilisearch index. 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 action ('Delete') and resource ('a Meilisearch index'), making the purpose immediately understandable. It distinguishes from siblings like 'delete-document' or 'delete-all-documents' by specifying the target is an index rather than documents. However, it doesn't explicitly differentiate from 'swap-indexes' which might also involve index removal, keeping it from a perfect score.

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 prerequisites (e.g., index must exist), consequences (e.g., data loss), or when to choose other deletion tools like 'delete-documents'. This lack of context leaves the agent without usage direction.

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/devlimelabs/meilisearch-ts-mcp'

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