Skip to main content
Glama
meilisearch

Meilisearch MCP Server

Official
by meilisearch

delete-index

Remove a specified Meilisearch index using its unique identifier (UID) to manage search data effectively.

Instructions

Delete a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes

Implementation Reference

  • MCP tool handler for 'delete-index': executes deletion via IndexManager and returns success confirmation.
    elif name == "delete-index":
        result = self.meili_client.indexes.delete_index(arguments["uid"])
        return [
            types.TextContent(
                type="text",
                text=f"Successfully deleted index: {arguments['uid']}",
            )
        ]
  • Registers the 'delete-index' tool in the list_tools handler, including its description and input schema (requires 'uid' string).
    types.Tool(
        name="delete-index",
        description="Delete a Meilisearch index",
        inputSchema={
            "type": "object",
            "properties": {"uid": {"type": "string"}},
            "required": ["uid"],
            "additionalProperties": False,
        },
    ),
  • IndexManager helper method that wraps the official Meilisearch client's delete_index(uid).
    def delete_index(self, uid: str) -> Dict[str, Any]:
        """Delete an index"""
        try:
            return self.client.delete_index(uid)
        except Exception as e:
            raise Exception(f"Failed to delete index: {str(e)}")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action is 'Delete,' implying a destructive mutation, but doesn't specify if this is irreversible, requires specific permissions, has side effects (e.g., deleting associated data), or provides confirmation feedback. This leaves critical behavioral traits unaddressed 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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, which is ideal for conciseness.

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 the tool's destructive nature, lack of annotations, no output schema, and minimal parameter guidance, the description is incomplete. It doesn't cover behavioral risks, success/error responses, or usage context, which are critical for safe and effective tool invocation in a system with multiple deletion-related tools.

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?

The description adds no parameter semantics beyond what the input schema provides. With 0% schema description coverage and 1 parameter ('uid'), the schema alone documents it as a required string. The description doesn't explain what 'uid' represents (e.g., index identifier), its format, or examples, but since there's only one parameter and the tool's purpose is straightforward, a baseline score of 3 is appropriate as the gap is minimal.

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 resource ('a Meilisearch index'), which is specific and unambiguous. However, it doesn't distinguish this tool from sibling tools like 'delete-key' or 'cancel-tasks' that also perform deletion operations, so it doesn't fully differentiate from alternatives.

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), exclusions, or comparisons to siblings like 'cancel-tasks' (which might handle deletion-related tasks) or 'list-indexes' (which could help identify indexes to delete).

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

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

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