Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

reset-embedders

Reset embedder configurations for a Meilisearch index to restore default settings and resolve embedding-related issues.

Instructions

Reset the embedders configuration for an index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that resets the embedders configuration by sending a DELETE request to the Meilisearch API endpoint for the specified index.
    async ({ indexUid }) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}/settings/embedders`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod schema defining the input parameter 'indexUid' as a required string.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Registration of the 'reset-embedders' tool on the MCP server, including name, description, input schema, and inline handler function.
    server.tool(
      "reset-embedders",
      "Reset the embedders configuration for an index",
      {
        indexUid: z.string().describe("Unique identifier of the index"),
      },
      async ({ indexUid }) => {
        try {
          const response = await apiClient.delete(`/indexes/${indexUid}/settings/embedders`);
          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 the full burden. It states 'reset' implies a mutation, but doesn't disclose behavioral traits such as whether this is destructive (e.g., removes custom embedders), requires specific permissions, has side effects, or returns any output. This leaves significant gaps for an agent to understand the tool's 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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and appropriately sized for its function, earning its place with zero waste.

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 complexity of a 'reset' operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'reset' entails (e.g., default values, side effects), the expected outcome, or error conditions, which are crucial for an agent to use this tool effectively in context with siblings like 'update-embedders'.

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 input schema has 100% description coverage, with 'indexUid' clearly documented as 'Unique identifier of the index'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting for parameter documentation.

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 ('reset') and the target ('embedders configuration for an index'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'update-embedders' or 'get-embedders', which would require mentioning what 'reset' entails compared to those operations.

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., whether the index must exist), consequences (e.g., if it reverts to defaults), or when to choose it over related tools like 'update-embedders' or 'get-embedders'.

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