Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-settings

Modify configuration parameters for a Meilisearch index by providing a JSON object with updated settings values.

Instructions

Update settings for a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
settingsYesJSON object containing settings to update

Implementation Reference

  • The handler function for the 'update-settings' tool. It validates and parses the settings JSON input, then sends a PATCH request to the Meilisearch API to update the index settings.
    async ({ indexUid, settings }) => {
      try {
        // Parse the settings string to ensure it's valid JSON
        const parsedSettings = JSON.parse(settings);
        
        // Ensure settings is an object
        if (typeof parsedSettings !== 'object' || parsedSettings === null || Array.isArray(parsedSettings)) {
          return {
            isError: true,
            content: [{ type: "text", text: "Settings must be a JSON object" }],
          };
        }
        
        const response = await apiClient.patch(`/indexes/${indexUid}/settings`, parsedSettings);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Input schema for the 'update-settings' tool using Zod, defining indexUid and settings parameters.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      settings: z.string().describe("JSON object containing settings to update"),
    },
  • Direct registration of the 'update-settings' tool on the MCP server within the registerSettingsTools function.
    server.tool(
      "update-settings",
      "Update settings for a Meilisearch index",
      {
        indexUid: z.string().describe("Unique identifier of the index"),
        settings: z.string().describe("JSON object containing settings to update"),
      },
      async ({ indexUid, settings }) => {
        try {
          // Parse the settings string to ensure it's valid JSON
          const parsedSettings = JSON.parse(settings);
          
          // Ensure settings is an object
          if (typeof parsedSettings !== 'object' || parsedSettings === null || Array.isArray(parsedSettings)) {
            return {
              isError: true,
              content: [{ type: "text", text: "Settings must be a JSON object" }],
            };
          }
          
          const response = await apiClient.patch(`/indexes/${indexUid}/settings`, parsedSettings);
          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 that invokes registerSettingsTools to add the 'update-settings' tool (among others) to the main MCP server instance.
    registerSettingsTools(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. It states 'Update' implies mutation but doesn't specify if changes are reversible, what permissions are required, or potential side effects (e.g., impact on search performance). This leaves significant gaps 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 that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every word contributing to clarity.

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 lacks details on behavioral traits (e.g., idempotency, error handling), expected response format, or how it interacts with sibling tools, leaving the agent with insufficient context for safe invocation.

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 fully documents both parameters ('indexUid' and 'settings'). The description adds no additional meaning beyond what's in the schema, such as format examples for the JSON settings or validation rules, meeting the baseline for high coverage.

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 ('Update') and target ('settings for a Meilisearch index'), providing a specific verb+resource combination. It distinguishes from siblings like 'get-settings' (read) and 'reset-settings' (reset to defaults), though it doesn't explicitly mention these alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'reset-settings' or 'get-settings'. The description lacks context about prerequisites (e.g., needing an existing index) or exclusions, offering only basic functional intent without usage boundaries.

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