Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-ranking-rules

Modify ranking rules to control how search results are ordered in a Meilisearch index, enabling custom relevance tuning.

Instructions

Update the ranking rules setting

Input Schema

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

Implementation Reference

  • Shared handler function for update-* tools, including update-ranking-rules. Parses the 'value' parameter as JSON and performs a PUT request to `/indexes/${indexUid}/settings/ranking-rules` using 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);
      }
    }
  • Zod input schema defining parameters: indexUid (string) and value (string containing JSON for the new ranking rules).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Configuration object for the 'update-ranking-rules' tool, specifying name, endpoint, and description, used within the updateSettingsTools array for dynamic tool registration.
    {
      name: "update-ranking-rules",
      endpoint: "ranking-rules",
      description: "Update the ranking rules setting",
    },
  • Dynamic registration loop that creates the server.tool call for 'update-ranking-rules' and other update tools using the configuration array.
    // 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 of all settings tools (including update-ranking-rules) by calling registerSettingsTools on the MCP server instance.
    registerSettingsTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update' implies a mutation, but the description doesn't specify whether this requires specific permissions, what happens to existing ranking rules, whether the change is immediate or asynchronous, or potential side effects. For a mutation tool with zero annotation coverage, this is a significant gap.

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. It's appropriately sized for a simple tool and front-loaded with the core action, though it lacks detail.

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 that this is a mutation tool with no annotations, no output schema, and a description that provides minimal context, the description is incomplete. It doesn't explain what ranking rules are, how they affect search, or what the tool returns, leaving significant gaps for an AI agent to understand and use it correctly.

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) with descriptions. The description adds no additional meaning beyond what the schema provides, such as explaining what 'ranking rules' are or the expected format of the 'value' JSON. 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.

Purpose3/5

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

The description states the action ('update') and resource ('ranking rules setting'), which provides a basic understanding of purpose. However, it's vague about what 'ranking rules' are or what this setting controls, and it doesn't distinguish this tool from similar update tools like 'update-settings' or 'update-searchable-attributes' in the sibling list.

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. The description doesn't mention prerequisites, when this operation is appropriate, or what other tools might be related (like 'get-ranking-rules' to check current rules or 'reset-ranking-rules' to revert to defaults).

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