Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

delete-document

Remove a document by its ID from a Meilisearch index to manage data and maintain search accuracy.

Instructions

Delete a document by its ID from a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
documentIdYesID of the document to delete

Implementation Reference

  • The handler function that performs the actual deletion of the specified document from the Meilisearch index via API call.
    async ({ indexUid, documentId }: DeleteDocumentParams) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}/documents/${documentId}`);
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema defining the parameters for the delete-document tool: indexUid and documentId.
    {
      indexUid: z.string().describe('Unique identifier of the index'),
      documentId: z.string().describe('ID of the document to delete'),
    },
  • The MCP server.tool registration for the delete-document tool, including name, description, schema, and handler.
    server.tool(
      'delete-document',
      'Delete a document by its ID from a Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index'),
        documentId: z.string().describe('ID of the document to delete'),
      },
      async ({ indexUid, documentId }: DeleteDocumentParams) => {
        try {
          const response = await apiClient.delete(`/indexes/${indexUid}/documents/${documentId}`);
          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 register all document tools, including delete-document, on the MCP server instance.
    registerDocumentTools(server);
  • TypeScript interface defining the parameters for delete-document operations.
    interface DeleteDocumentParams {
      indexUid: string;
      documentId: 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 the destructive action ('Delete') but doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, authentication requirements, rate limits, error handling (e.g., if document doesn't exist), or what happens to associated data. For a destructive 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's front-loaded with the core action and target, making it easy to parse. Every word earns its place without redundancy.

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 doesn't cover behavioral aspects (permanence, errors), usage context vs. siblings, or return values. Given the complexity of deletion operations and lack of structured data, more guidance is needed.

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 both parameters ('indexUid', 'documentId') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (it doesn't explain format, constraints, or examples). Baseline 3 is appropriate when 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 target ('a document by its ID from a Meilisearch index'), providing specific verb+resource. However, it doesn't explicitly distinguish this tool from its sibling 'delete-documents' (plural), which appears to handle multiple document deletions. The purpose is clear but lacks sibling differentiation.

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 'delete-documents' (for multiple deletions) or 'delete-all-documents' (for bulk removal). It doesn't mention prerequisites, error conditions, or contextual constraints. Usage is implied by the name but not explicitly stated.

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