Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

reset-searchable-attributes

Restore default searchable attributes for a Meilisearch index to control which fields are searchable, ensuring consistent search behavior.

Instructions

Reset the searchable attributes setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Shared handler function for all reset-specific-settings tools, including 'reset-searchable-attributes'. It deletes the specified setting endpoint via the API client.
    async ({ indexUid }) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}/settings/${endpoint}`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Input schema for the reset-searchable-attributes tool: requires indexUid.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Tool configuration entry defining the name, endpoint, and description for 'reset-searchable-attributes'.
    {
      name: "reset-searchable-attributes",
      endpoint: "searchable-attributes",
      description: "Reset the searchable attributes setting to its default value",
    },
  • Registration loop that creates and registers the 'reset-searchable-attributes' tool (and others) on the MCP server using the shared handler and schema.
    resetSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
        },
        async ({ indexUid }) => {
          try {
            const response = await apiClient.delete(`/indexes/${indexUid}/settings/${endpoint}`);
            return {
              content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
    });
  • src/index.ts:67-67 (registration)
    Top-level call to register all settings tools, including 'reset-searchable-attributes', on the MCP server.
    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. It mentions 'reset' which implies a mutation, but doesn't disclose behavioral traits like whether this requires specific permissions, is reversible, has side effects, or what happens to existing settings. The description is minimal and lacks details on rate limits, error conditions, or response format.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and target, making it easy to parse. Every part of the sentence contributes essential information, earning its place.

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 tool involves mutation (reset) with no annotations and no output schema, the description is incomplete. It doesn't explain what the default value is, how the reset affects search functionality, or what the response looks like. For a mutation tool in a context with many sibling settings tools, more context is needed to guide proper use.

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 the single parameter 'indexUid' documented in the schema as 'Unique identifier of the index'. The description adds no additional meaning about parameters beyond what the schema provides, such as format examples or constraints. Baseline score of 3 is appropriate given high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('reset') and the target ('searchable attributes setting'), specifying it sets to 'default value'. It distinguishes from sibling tools like 'update-searchable-attributes' by focusing on resetting rather than updating, though it doesn't explicitly name alternatives. The purpose is specific and understandable.

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 'update-searchable-attributes' or 'get-searchable-attributes'. It lacks context about prerequisites, such as when a reset is needed or what the default value entails. Usage is implied only by the action 'reset', with no explicit when/when-not statements.

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