Skip to main content
Glama
meilisearch

Meilisearch MCP Server

Official
by meilisearch

delete-key

Remove an API key from the Meilisearch MCP Server to ensure secure access control and manage user permissions effectively.

Instructions

Delete an API key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Implementation Reference

  • Handler for the 'delete-key' tool: calls meili_client.keys.delete_key with the provided key and returns a success message.
    elif name == "delete-key":
        self.meili_client.keys.delete_key(arguments["key"])
        return [
            types.TextContent(
                type="text",
                text=f"Successfully deleted API key: {arguments['key']}",
            )
        ]
  • Input schema definition for the 'delete-key' tool, requiring a 'key' parameter.
    types.Tool(
        name="delete-key",
        description="Delete an API key",
        inputSchema={
            "type": "object",
            "properties": {"key": {"type": "string"}},
            "required": ["key"],
            "additionalProperties": False,
        },
    ),
  • KeyManager helper method that wraps the Meilisearch client's delete_key method with error handling.
    def delete_key(self, key: str) -> None:
        """Delete an API key"""
        try:
            return self.client.delete_key(key)
        except Exception as e:
            raise Exception(f"Failed to delete key: {str(e)}")
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. 'Delete' implies a destructive, irreversible mutation, but the description doesn't specify permissions required, confirmation prompts, error conditions, or what happens on success/failure. This leaves critical behavioral traits undocumented.

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 zero wasted words. It's appropriately sized for a simple destructive operation and front-loads the essential action. Every word earns its place.

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, 0% schema coverage, and no output schema, the description is inadequate. It lacks critical context: what the 'key' parameter means, behavioral details (permissions, irreversibility), and expected outcomes. The agent cannot safely invoke this tool based solely on the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'key' represents (e.g., key ID, name, or full API key), format expectations, or validation rules. The single parameter remains semantically opaque beyond its name.

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 resource ('an API key'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create-key' and 'get-keys' by specifying the destructive operation. However, it doesn't specify whether this deletes a single key or all keys, which prevents a perfect score.

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., needing an existing key), exclusions, or related tools like 'get-keys' for verification. The agent must infer usage from the tool name alone.

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