Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-searchable-attributes

Configure which attributes are searchable in a Meilisearch index to control search relevance and performance.

Instructions

Update the searchable attributes setting

Input Schema

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

Implementation Reference

  • Handler function that executes the tool: parses JSON value, PUTs to Meilisearch API endpoint for searchable-attributes, returns response.
    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 for indexUid and value parameters.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Tool configuration object specifying name, endpoint, and description, used in forEach to register the tool.
    {
      name: "update-searchable-attributes",
      endpoint: "searchable-attributes",
      description: "Update the searchable attributes setting",
    },
  • src/index.ts:67-67 (registration)
    Top-level call to registerSettingsTools which includes registration of update-searchable-attributes tool.
    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 full burden. 'Update' implies a mutation operation, but the description doesn't disclose behavioral traits like required permissions, whether changes are immediate or asynchronous, what happens to existing settings, or error conditions. For a mutation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 front-loaded with the core action. However, it could be slightly more informative without sacrificing conciseness, such as by clarifying the scope of 'searchable attributes'.

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 doesn't explain what searchable attributes are, how updates affect search behavior, or what the tool returns. Given the complexity of managing index settings and the lack of structured behavioral data, more context is needed.

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%, with both parameters clearly documented in the schema. The description adds no additional meaning about parameters beyond what's in the schema (e.g., format of 'value', examples of valid JSON). Baseline 3 is appropriate when 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 'Update the searchable attributes setting' clearly states the action (update) and target (searchable attributes setting), but it's vague about what 'searchable attributes' are and doesn't distinguish this tool from its sibling 'reset-searchable-attributes' or other update-* tools. It provides basic purpose but lacks specificity about the resource being modified.

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 provides no guidance on when to use this tool versus alternatives like 'reset-searchable-attributes' or 'get-searchable-attributes', nor does it mention prerequisites or context. With multiple sibling tools for managing searchable attributes, this omission leaves the agent without direction on tool selection.

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