Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-sortable-attributes

Configure which fields can be used to sort search results in a Meilisearch index. Specify the index and JSON array of sortable attributes to customize search result ordering.

Instructions

Update the sortable attributes setting

Input Schema

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

Implementation Reference

  • The handler function for the 'update-sortable-attributes' tool (shared with other update tools). Parses the input value as JSON and sends a PUT request to the Meilisearch API to update the sortable-attributes setting for the specified 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 validation using Zod for the update tools, including indexUid and value parameters.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • The registration loop that dynamically registers the 'update-sortable-attributes' tool (and others) with the MCP server using server.tool().
    // 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);
          }
        }
      );
  • Configuration object in the updateSettingsTools array that specifies the name, endpoint, and description for the 'update-sortable-attributes' tool.
    {
      name: "update-sortable-attributes",
      endpoint: "sortable-attributes",
      description: "Update the sortable attributes setting",
    },
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. It mentions 'Update' which implies a mutation, but doesn't disclose critical traits like whether this requires specific permissions, if it's destructive to existing data, what the response format is, or if it triggers asynchronous tasks (common in sibling tools like 'update-documents'). This leaves significant gaps in understanding the tool's behavior.

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 zero wasted words. It's front-loaded with the key action ('Update'), making it easy to parse quickly, though this conciseness comes at the cost of 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 the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what sortable attributes are, how the update affects search functionality, or what the return value looks like. With many sibling tools for similar operations, more context is needed to distinguish and use this tool effectively.

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?

The input schema has 100% description coverage, with clear documentation for 'indexUid' and 'value' parameters. The description adds no additional semantic meaning beyond the schema, such as explaining the JSON structure for 'value' or how it relates to sortable attributes. 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.

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 the target ('the sortable attributes setting'), which provides a basic understanding of purpose. However, it doesn't specify what 'sortable attributes' are or how they differ from other settings like 'searchable attributes' or 'filterable attributes' among the many sibling tools, leaving the purpose somewhat vague.

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?

The description offers no guidance on when to use this tool versus alternatives. With siblings like 'get-sortable-attributes' (for retrieval) and 'reset-sortable-attributes' (for resetting), it fails to clarify the context or prerequisites for updating, such as after retrieving current settings or before resetting.

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