Skip to main content
Glama
meilisearch

Meilisearch MCP Server

Official
by meilisearch

list-indexes

Retrieve all indexes from a Meilisearch server to manage and organize search data efficiently. Ideal for maintaining structured search environments.

Instructions

List all Meilisearch indexes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'list-indexes' tool in the list_tools handler, including its name, description, and input schema (empty object).
    types.Tool(
        name="list-indexes",
        description="List all Meilisearch indexes",
        inputSchema={
            "type": "object",
            "properties": {},
            "additionalProperties": False,
        },
    ),
  • The MCP tool handler for 'list-indexes' which retrieves indexes using the client and returns formatted JSON output.
    elif name == "list-indexes":
        indexes = self.meili_client.get_indexes()
        formatted_json = json.dumps(
            indexes, indent=2, default=json_serializer
        )
        return [
            types.TextContent(
                type="text", text=f"Indexes:\n{formatted_json}"
            )
        ]
  • Helper method in MeilisearchClient that fetches indexes from the Meilisearch library client and serializes them into a JSON-friendly dictionary format.
    def get_indexes(self) -> Dict[str, Any]:
        """Get all indexes"""
        indexes = self.client.get_indexes()
        # Convert Index objects to serializable dictionaries
        serialized_indexes = []
        for index in indexes["results"]:
            serialized_indexes.append(
                {
                    "uid": index.uid,
                    "primaryKey": index.primary_key,
                    "createdAt": index.created_at,
                    "updatedAt": index.updated_at,
                }
            )
    
        return {
            "results": serialized_indexes,
            "offset": indexes["offset"],
            "limit": indexes["limit"],
            "total": indexes["total"],
        }
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 mentions that it 'List all Meilisearch indexes,' which implies a read-only operation, but doesn't specify whether it returns all indexes at once, uses pagination, requires authentication, or has rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 no wasted words. It's front-loaded with the key action and resource, making it easy to understand at a glance. Every part of the sentence contributes directly to explaining the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks details on behavioral aspects like return format or usage context. For a read operation in a server with many sibling tools, more guidance on when to use it would enhance completeness.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it appropriately focuses on the tool's purpose. Since there are no parameters, the baseline is 4, as the description doesn't mislead or omit necessary parameter information.

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 ('List all') and resource ('Meilisearch indexes'), making the purpose immediately understandable. It distinguishes from siblings like 'get-index-metrics' or 'get-stats' by focusing specifically on listing indexes rather than retrieving metrics or statistics. However, it doesn't explicitly differentiate from 'create-index' or 'delete-index' beyond the verb choice.

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 'get-index-metrics' or 'get-stats', nor does it mention prerequisites or context for usage. It simply states what the tool does without indicating when it's appropriate to invoke it in relation to other tools.

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