Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-searchable-attributes

Restore searchable attributes to default settings in a Meilisearch index to fix search behavior or configuration issues.

Instructions

Reset the searchable attributes setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the tool logic: sends a DELETE request to the Meilisearch API to reset the searchable-attributes setting for the given 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);
      }
    }
  • Zod schema defining the input parameter 'indexUid' for the tool.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object specifying the tool name, endpoint, and description, used in the registration loop for reset tools.
    {
      name: "reset-searchable-attributes",
      endpoint: "searchable-attributes",
      description: "Reset the searchable attributes setting to its default value",
    },
  • Registration loop that dynamically registers the server.tool for all reset settings tools, including reset-searchable-attributes, with shared schema and handler template.
    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 invocation of the settings tools registration function on the MCP server instance.
    registerSettingsTools(server);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('reset'), suggesting it changes settings, but doesn't specify if this requires admin permissions, whether it's reversible, what the default value entails, or any rate limits. This is a significant gap for a tool that likely modifies system configuration.

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, direct sentence with no wasted words. It front-loads the key action ('reset') and target, making it efficient and easy to parse. Every part of the sentence contributes essential information.

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 tool that resets settings (a mutation), the description is incomplete. With no annotations and no output schema, it lacks details on behavioral aspects like permissions, side effects, or what happens after resetting. It also doesn't explain the broader context of 'searchable attributes' or how this fits with sibling tools, leaving gaps in understanding.

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?

The input schema has 100% description coverage, with 'indexUid' clearly documented as the 'Unique identifier of the index'. The description doesn't add any meaning beyond this, such as explaining what an 'index' is in this context or how to obtain the 'indexUid'. Given the high schema coverage, a baseline score of 3 is appropriate.

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 to its default value'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'reset-filterable-attributes' or 'update-searchable-attributes', which would require more specific context about what 'searchable attributes' are.

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. For example, it doesn't mention when to choose 'reset-searchable-attributes' over 'update-searchable-attributes' or 'get-searchable-attributes', nor does it specify prerequisites like needing an existing index. This leaves the agent without clear usage context.

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