Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

update-synonyms

Modify synonyms in a Meilisearch index to improve search relevance by mapping related terms for better query matching.

Instructions

Update the synonyms setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
valueYesJSON value for the setting

Implementation Reference

  • Handler function for the 'update-synonyms' tool. Parses the provided JSON string 'value' as synonyms and sends a PUT request to update the synonyms setting in the specified Meilisearch index.
    async ({ indexUid, value }) => {
      try {
        // Parse the value string to ensure it's valid JSON
        const parsedValue = JSON.parse(value);
        
        const response = await apiClient.put(`/indexes/${indexUid}/settings/${endpoint}`, parsedValue);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Input schema using Zod for the update-synonyms tool: requires indexUid (string) and value (string containing JSON for synonyms).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Registration logic for 'update-synonyms' (and other update tools) via a forEach loop calling server.tool with the tool name from updateSettingsTools array (where update-synonyms is defined at lines 200-204), shared schema, and shared handler.
    updateSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
          value: z.string().describe("JSON value for the setting"),
        },
        async ({ indexUid, value }) => {
          try {
            // Parse the value string to ensure it's valid JSON
            const parsedValue = JSON.parse(value);
            
            const response = await apiClient.put(`/indexes/${indexUid}/settings/${endpoint}`, parsedValue);
            return {
              content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
    });
  • Configuration object in the updateSettingsTools array specifically for the 'update-synonyms' tool, providing its name, the Meilisearch endpoint '/synonyms', and description used during registration.
    {
      name: "update-synonyms",
      endpoint: "synonyms",
      description: "Update the synonyms setting",
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Update' implies a mutation operation, but the description doesn't disclose any behavioral traits: whether this requires specific permissions, whether it overwrites or merges with existing synonyms, what format the JSON value should be in, whether changes are immediate or asynchronous, or what happens on error. For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise at just 4 words. While this brevity contributes to under-specification in other dimensions, the text itself contains no wasted words and is front-loaded with the core action. Every word ('Update', 'the', 'synonyms', 'setting') serves a basic grammatical purpose, making it structurally efficient.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'update' means operationally, what the JSON value format should be, whether the operation is synchronous or returns a task ID (common in this sibling tool context), or what happens on success/failure. For a tool that modifies search index settings, this minimal description leaves critical gaps.

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%, with both parameters clearly documented in the schema (indexUid as 'Unique identifier of the index', value as 'JSON value for the setting'). The description adds no additional meaning about parameters beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update the synonyms setting' is a tautology that essentially restates the tool name 'update-synonyms'. It doesn't specify what resource is being updated (index synonyms), what 'update' entails (replace, modify, add?), or how this differs from sibling tools like 'get-synonyms' or 'reset-synonyms'. The purpose is minimally stated but lacks specificity and differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is zero guidance about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing index), when this should be used instead of 'reset-synonyms', or what happens if synonyms are already configured. With multiple sibling tools related to synonyms (get-synonyms, reset-synonyms), this lack of differentiation is problematic.

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