Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

delete-documents

Remove multiple documents by their IDs from a Meilisearch index to manage data and maintain search relevance.

Instructions

Delete multiple documents by their IDs from a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
documentIdsYesJSON array of document IDs to delete

Implementation Reference

  • Handler function that parses the provided documentIds (JSON string) into an array and deletes the batch using the Meilisearch API.
    async ({ indexUid, documentIds }: DeleteDocumentsParams) => {
      try {
        // Parse the document IDs string to ensure it's valid JSON
        const parsedDocumentIds = JSON.parse(documentIds);
        
        // Ensure document IDs is an array
        if (!Array.isArray(parsedDocumentIds)) {
          return {
            isError: true,
            content: [{ type: 'text', text: 'Document IDs must be a JSON array' }],
          };
        }
        
        const response = await apiClient.post(`/indexes/${indexUid}/documents/delete-batch`, parsedDocumentIds);
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the delete-documents tool.
    {
      indexUid: z.string().describe('Unique identifier of the index'),
      documentIds: z.string().describe('JSON array of document IDs to delete'),
    },
  • TypeScript interface for the parameters used in the handler.
    interface DeleteDocumentsParams {
      indexUid: string;
      documentIds: string;
    }
  • src/index.ts:65-65 (registration)
    Top-level registration call that invokes the document tools registration, including delete-documents.
    registerDocumentTools(server);
  • Specific registration of the delete-documents tool using server.tool, including schema and handler.
    server.tool(
      'delete-documents',
      'Delete multiple documents by their IDs from a Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index'),
        documentIds: z.string().describe('JSON array of document IDs to delete'),
      },
      async ({ indexUid, documentIds }: DeleteDocumentsParams) => {
        try {
          // Parse the document IDs string to ensure it's valid JSON
          const parsedDocumentIds = JSON.parse(documentIds);
          
          // Ensure document IDs is an array
          if (!Array.isArray(parsedDocumentIds)) {
            return {
              isError: true,
              content: [{ type: 'text', text: 'Document IDs must be a JSON array' }],
            };
          }
          
          const response = await apiClient.post(`/indexes/${indexUid}/documents/delete-batch`, parsedDocumentIds);
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
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 the action is destructive ('Delete'), but lacks details on permissions needed, whether deletion is permanent or reversible, rate limits, or what happens if IDs don't exist. For a mutation tool with zero annotation coverage, this is a significant gap.

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 front-loads the key action and resource, making it immediately clear 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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., permanence, error handling), usage differentiation from siblings, and output expectations, leaving significant gaps for an AI agent to operate safely.

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%, so the schema already documents both parameters ('indexUid' and 'documentIds'). The description adds no additional meaning beyond what the schema provides, such as format examples for 'documentIds' or context about index selection. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Delete multiple documents') and target resource ('from a Meilisearch index'), distinguishing it from sibling tools like 'delete-document' (singular) and 'delete-all-documents' (all documents). It precisely communicates the verb and scope.

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 on when to use this tool versus alternatives like 'delete-document' (for single documents) or 'delete-all-documents' (for all documents). The description mentions 'multiple documents' but doesn't explicitly differentiate from these siblings or specify 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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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