Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

update-searchable-attributes

Modify which fields in a Meilisearch index are used for search queries to improve 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

  • Shared handler for update tools: parses JSON value input, performs PUT request to `/indexes/${indexUid}/settings/searchable-attributes` using apiClient, returns JSON response or error.
    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, Meilisearch index UID), value (string, JSON-serialized setting value).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Tool configuration in updateSettingsTools array: specifies name, endpoint ("searchable-attributes"), and description for dynamic server.tool() registration.
    {
      name: "update-searchable-attributes",
      endpoint: "searchable-attributes",
      description: "Update the searchable attributes setting",
    },
  • src/index.ts:67-67 (registration)
    Top-level call to registerSettingsTools(server), which dynamically registers the "update-searchable-attributes" tool via the loop in settings-tools.ts.
    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 but offers minimal behavioral insight. It implies a mutation ('update') but doesn't disclose permissions needed, whether changes are reversible, rate limits, or what the response looks like. For a write operation with zero annotation coverage, this leaves significant gaps in understanding tool 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 appropriately sized for a simple update operation and front-loads the key action and target.

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 a mutation tool with no annotations, no output schema, and 100% schema coverage, the description is incomplete. It lacks context on behavioral traits (e.g., side effects, error handling), usage guidelines, and doesn't compensate for the absence of structured safety or response information.

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 ('indexUid', 'value') clearly documented in the schema. The description adds no additional meaning beyond the schema, such as explaining the JSON format for 'value' or providing examples. 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 somewhat vague about what 'searchable attributes' means in this context. It distinguishes from siblings like 'get-searchable-attributes' (read vs. write) but doesn't specify what exactly gets updated beyond the general setting.

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. It doesn't mention prerequisites (e.g., needing an existing index), exclusions, or comparisons to sibling tools like 'reset-searchable-attributes' or 'update-settings'. The agent must infer usage from context alone.

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/devlimelabs/meilisearch-ts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server