Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

delete-all-documents

Remove all documents from a Meilisearch index to clear data or reset content. Specify the index identifier to perform this bulk deletion operation.

Instructions

Delete all documents in a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that performs the deletion of all documents in the specified Meilisearch index by calling apiClient.delete on the `/indexes/{indexUid}/documents` endpoint.
    async ({ indexUid }: DeleteAllDocumentsParams) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}/documents`);
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema for the delete-all-documents tool, defining the required indexUid parameter.
    {
      indexUid: z.string().describe('Unique identifier of the index'),
    },
  • Direct registration of the 'delete-all-documents' tool on the MCP server, including name, description, schema, and handler.
      'delete-all-documents',
      'Delete all documents in a Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index'),
      },
      async ({ indexUid }: DeleteAllDocumentsParams) => {
        try {
          const response = await apiClient.delete(`/indexes/${indexUid}/documents`);
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:65-65 (registration)
    Top-level call to registerDocumentTools(server), which includes registration of the delete-all-documents tool.
    registerDocumentTools(server);
  • TypeScript interface defining the parameters for the delete-all-documents tool handler.
    interface DeleteAllDocumentsParams {
      indexUid: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It indicates a destructive operation ('Delete all documents'), but lacks details about permissions needed, whether the action is reversible, rate limits, or what happens to the index structure. This is a significant gap for a high-impact mutation tool.

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 directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded with the essential information.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain the consequences of deletion, whether documents are permanently removed, what the response looks like, or any safety considerations. More context is needed given the tool's complexity and impact.

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% for the single parameter 'indexUid', so the schema already documents it adequately. The description doesn't add any additional meaning about the parameter beyond what's in the schema, which meets the baseline expectation when schema coverage is high.

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 all documents') and the target resource ('in a Meilisearch index'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete-document' (singular) or 'delete-documents' (batch), which would require a 5.

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?

No guidance is provided about when to use this tool versus alternatives like 'delete-document' or 'delete-documents'. The description only states what it does without context about appropriate use cases or prerequisites.

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