Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-displayed-attributes

Configure which document fields appear in search results by updating displayed attributes for a Meilisearch index.

Instructions

Update the displayed attributes setting

Input Schema

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

Implementation Reference

  • Handler function that parses the JSON value and performs a PUT request to the Meilisearch API endpoint `/indexes/{indexUid}/settings/displayed-attributes` to update the displayed attributes.
    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 the tool parameters: indexUid (string) and value (JSON string for the new displayed attributes).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Registration of the update-displayed-attributes tool via the forEach loop over updateSettingsTools, using server.tool() with name, description, schema, and handler.
    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 entry in updateSettingsTools array that defines the tool's name, endpoint ('displayed-attributes'), and description for registration.
    {
      name: "update-displayed-attributes",
      endpoint: "displayed-attributes",
      description: "Update the displayed attributes setting",
    },
  • src/index.ts:67-67 (registration)
    Top-level invocation of registerSettingsTools(server), which registers all settings tools including 'update-displayed-attributes'.
    registerSettingsTools(server);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
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. It states 'Update' implying a mutation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, potential side effects, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 front-loaded with the core action and resource, making it easy to parse quickly.

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 incomplete behavioral disclosure, the description is insufficient. It lacks context on what 'displayed attributes' are, how updates behave, or what to expect in return, making it hard for an agent to use 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'). The description adds no meaning beyond this, such as explaining what 'value' should contain (e.g., JSON format details) or how it affects displayed attributes. 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 the resource ('displayed attributes setting'), which clarifies the tool's purpose. However, it's vague about what 'displayed attributes' are or what this setting controls, and it doesn't differentiate from sibling tools like 'get-displayed-attributes' or 'reset-displayed-attributes' beyond the verb.

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 related tools like 'reset-displayed-attributes' or 'get-displayed-attributes', leaving usage unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.