Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-filterable-attributes

Modify which fields can be used to filter search results in a Meilisearch index, enabling precise data retrieval through attribute-based filtering.

Instructions

Update the filterable attributes setting

Input Schema

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

Implementation Reference

  • Handler that parses the JSON value input, performs a PUT request to update the filterable-attributes setting via apiClient, and returns the 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);
      }
    }
  • Zod input schema defining indexUid and value parameters.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Registration loop that dynamically registers the update-filterable-attributes tool (along with others) using server.tool, including its specific endpoint 'filterable-attributes'.
    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);
          }
        }
      );
    });
  • Specific configuration object in updateSettingsTools array that defines the name, endpoint, and description for the tool.
    {
      name: "update-filterable-attributes",
      endpoint: "filterable-attributes",
      description: "Update the filterable 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 full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't reveal whether this requires specific permissions, whether changes are reversible, what happens to existing filterable attributes not mentioned, or if there are rate limits. For a mutation tool with zero annotation coverage, this represents a significant behavioral information 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 extremely concise - a single sentence with no wasted words. It's front-loaded with the core action and resource. While under-specified in content, it achieves perfect efficiency in form with zero redundancy or unnecessary elaboration.

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 this is a mutation tool with no annotations, no output schema, and multiple sibling tools for similar operations, the description is incomplete. It doesn't explain what filterable attributes are, what format the JSON value should take, what the tool returns, or how it differs from reset-filterable-attributes. For a tool that modifies index configuration, this level of documentation is inadequate.

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 and value) clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description 'Update the filterable attributes setting' is essentially a tautology that restates the tool name with minimal added value. While it includes a verb ('Update') and resource ('filterable attributes setting'), it lacks specificity about what this setting controls or what 'filterable attributes' means in this context. It doesn't distinguish this tool from sibling update tools like update-displayed-attributes or update-searchable-attributes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. There's no mention of prerequisites (like needing an existing index), when this operation is appropriate, or what happens if used incorrectly. With multiple sibling tools for updating various index settings, the absence of any comparative context leaves the agent without usage direction.

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