Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-stop-words

Modify stop words for a Meilisearch index to exclude common terms from search results, improving relevance by filtering out non-meaningful words.

Instructions

Update the stop words setting

Input Schema

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

Implementation Reference

  • Handler logic for the update-stop-words tool: parses JSON value and sends PUT request to /indexes/{indexUid}/settings/stop-words via apiClient, returns formatted response or handles errors.
    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: indexUid (string), value (string as JSON). Used for all update-* tools including update-stop-words.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Tool configuration object in updateSettingsTools array defining name, endpoint, and description for update-stop-words.
    {
      name: "update-stop-words",
      endpoint: "stop-words",
      description: "Update the stop words setting",
    },
  • forEach loop that registers the update-stop-words tool (and others) by calling server.tool with name, description, schema, and shared handler using the endpoint 'stop-words'.
    // 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);
          }
        }
      );
  • src/index.ts:67-67 (registration)
    Top-level registration call to registerSettingsTools(server), which registers all settings tools including update-stop-words.
    registerSettingsTools(server);
Behavior2/5

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

With no annotations, the description carries full burden but only states 'update' without clarifying behavioral traits. It doesn't disclose if this is a destructive operation, requires specific permissions, has side effects, or how it interacts with other settings, leaving significant gaps in transparency for a mutation tool.

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 no wasted words, making it appropriately concise and front-loaded. It directly states the tool's action without unnecessary elaboration.

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 lacks details on what stop words are, how the update affects search behavior, error conditions, or return values, making it inadequate for safe and effective use.

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' and 'value'). The description adds no additional meaning beyond what's in the schema, such as explaining the format of 'value' or its impact, meeting the baseline for high schema coverage.

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 stop words setting' restates the tool name with minimal elaboration, making it tautological. It specifies the action ('update') and resource ('stop words setting'), but lacks detail on what stop words are or how this differs from sibling tools like 'get-stop-words' or 'reset-stop-words', leaving the purpose vague.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or how it compares to sibling tools like 'reset-stop-words' or 'get-stop-words', offering no usage context.

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