Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-synonyms

Modify search synonyms in a Meilisearch index to improve query matching and enhance search relevance.

Instructions

Update the synonyms setting

Input Schema

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

Implementation Reference

  • Configuration object defining the 'update-synonyms' tool, specifying its name, endpoint ('synonyms'), and description for registration.
    {
      name: "update-synonyms",
      endpoint: "synonyms",
      description: "Update the synonyms setting",
    },
  • Zod input schema for the 'update-synonyms' tool, requiring indexUid (string) and value (JSON string for synonyms).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Handler function for 'update-synonyms': parses JSON value and performs PUT request to `/indexes/{indexUid}/settings/synonyms` via apiClient.
    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);
      }
    }
  • Loop that registers the 'update-synonyms' tool (and others) by calling server.tool with dynamic name, endpoint 'synonyms', shared schema, and handler.
    // Create an update tool for each specific setting
    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);
          }
        }
      );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'Update' implies a mutation operation, but there's no information about permissions required, whether this is destructive/reversible, rate limits, side effects, or what happens to existing synonym configurations. For a mutation tool with zero annotation coverage, this is critically 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 comes at the cost of completeness, it's front-loaded and contains no wasted words. Every word contributes directly to the core statement, making it structurally efficient despite being informationally sparse.

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

Completeness1/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, no output schema, and a vague description, the contextual information is severely incomplete. The description doesn't explain what 'synonyms setting' means, what format the JSON value should take, what the tool returns, or how it differs from related operations. For a tool that modifies search/index configuration, this level of documentation is inadequate.

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 both parameters (indexUid and value) are documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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' means (replace, add, modify?), or how this differs from sibling tools like 'get-synonyms' or 'reset-synonyms'. The verb+resource combination is too vague for proper 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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple related tools like 'get-synonyms', 'reset-synonyms', and 'update-settings' that likely interact with synonyms, but the description offers no context about when this specific tool is appropriate versus those alternatives. No prerequisites, constraints, or comparison information is provided.

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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server