Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

update-embedders

Configure embedders for vector search in Meilisearch indexes to enable semantic search capabilities.

Instructions

Configure embedders for vector search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
embeddersYesJSON object containing embedder configurations

Implementation Reference

  • The main handler function for the 'update-embedders' tool. It parses the embedders JSON input, validates it as an object, and sends a PATCH request to the Meilisearch API to update the embedders configuration for the specified index.
    async ({ indexUid, embedders }) => {
      try {
        // Parse the embedders string to ensure it's valid JSON
        const parsedEmbedders = JSON.parse(embedders);
        
        // Ensure embedders is an object
        if (typeof parsedEmbedders !== 'object' || parsedEmbedders === null || Array.isArray(parsedEmbedders)) {
          return {
            isError: true,
            content: [{ type: "text", text: "Embedders must be a JSON object" }],
          };
        }
        
        const response = await apiClient.patch(`/indexes/${indexUid}/settings/embedders`, parsedEmbedders);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod schema defining the input parameters for the tool: indexUid (string) and embedders (string representing a JSON object).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      embedders: z.string().describe("JSON object containing embedder configurations"),
    },
  • Direct registration of the 'update-embedders' tool on the MCP server using server.tool(), specifying name, description, input schema, and handler function.
    server.tool(
      "update-embedders",
      "Configure embedders for vector search",
      {
        indexUid: z.string().describe("Unique identifier of the index"),
        embedders: z.string().describe("JSON object containing embedder configurations"),
      },
      async ({ indexUid, embedders }) => {
        try {
          // Parse the embedders string to ensure it's valid JSON
          const parsedEmbedders = JSON.parse(embedders);
          
          // Ensure embedders is an object
          if (typeof parsedEmbedders !== 'object' || parsedEmbedders === null || Array.isArray(parsedEmbedders)) {
            return {
              isError: true,
              content: [{ type: "text", text: "Embedders must be a JSON object" }],
            };
          }
          
          const response = await apiClient.patch(`/indexes/${indexUid}/settings/embedders`, parsedEmbedders);
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:68-68 (registration)
    Top-level registration call that invokes registerVectorTools(server), which in turn registers the 'update-embedders' tool along with other vector tools.
    registerVectorTools(server);
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. 'Configure' implies a mutation/write operation, but the description doesn't specify whether this requires admin permissions, whether changes are immediate or asynchronous, what happens to existing embedder settings, or potential side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 wasted words. It's appropriately sized for a simple configuration tool and front-loads the essential information.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what successful configuration entails, whether it returns confirmation data, how errors are handled, or how it interacts with vector search functionality. The context signals indicate this is a 2-parameter tool with 100% schema coverage, but the description fails to compensate for missing behavioral and output information.

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%, so the schema already documents both parameters (indexUid, embedders) with their types and purposes. The description doesn't add any meaningful parameter semantics beyond what's in the schema, such as format examples for embedders JSON or relationships between parameters. Baseline 3 is appropriate when 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 ('Configure') and resource ('embedders for vector search'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get-embedders' (read) or 'reset-embedders' (reset to defaults), which would be needed for 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 like 'reset-embedders' or 'get-embedders'. It doesn't mention prerequisites (e.g., needing an existing index), exclusions, or appropriate contexts for configuration changes.

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