Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

delete-index

Remove a Meilisearch index by specifying its unique identifier to free up resources and manage your search database structure.

Instructions

Delete a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index to delete

Implementation Reference

  • The handler function for the 'delete-index' tool. It deletes the specified index using the apiClient and returns the response or handles errors.
    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 for the 'delete-index' tool requiring indexUid.
    {
      indexUid: z.string().describe('Unique identifier of the index to delete'),
    },
  • Module-level registration of the 'delete-index' tool using server.tool() including schema and handler.
    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);
        }
      }
    );
  • TypeScript interface defining the input parameters for the delete-index handler.
    interface DeleteIndexParams {
      indexUid: string;
    }
  • src/index.ts:64-64 (registration)
    Top-level registration call that invokes the index tools registration, including 'delete-index'.
    registerIndexTools(server);
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. While 'Delete' implies a destructive mutation, it lacks details on permissions required, whether deletion is reversible, rate limits, or what happens to associated data. This is inadequate for a destructive operation.

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, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 destructive tool with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like safety warnings, expected outcomes, or error conditions, leaving critical gaps for an AI agent to understand the tool's full context.

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 parameter 'indexUid' well-documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline score of 3 for high schema coverage.

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 the resource ('a Meilisearch index'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete-document' or 'delete-all-documents', which also perform deletion operations on related resources.

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., permanent deletion), or when to choose other deletion tools like 'delete-document' for partial data removal.

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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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