Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-searchable-attributes

Retrieve the searchable attributes configuration for a Meilisearch index to understand which fields can be queried in search operations.

Instructions

Get the searchable attributes setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the tool logic: fetches the 'searchable-attributes' setting from the Meilisearch API for the given indexUid.
    async ({ indexUid }) => {
      try {
        const response = await apiClient.get(`/indexes/${indexUid}/settings/${endpoint}`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
  • Input schema definition using Zod: requires indexUid as a string.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in specificSettingsTools array that defines the tool's name, Meilisearch endpoint, and description for registration.
    {
      name: "get-searchable-attributes",
      endpoint: "searchable-attributes",
      description: "Get the searchable attributes setting",
    },
  • ForEach loop that registers the 'get-searchable-attributes' tool (and others) with the MCP server using the configuration, schema, and handler.
    // Create a tool for each specific setting
    specificSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
        },
        async ({ indexUid }) => {
          try {
            const response = await apiClient.get(`/indexes/${indexUid}/settings/${endpoint}`);
            return {
              content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
    });
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 only states the action ('Get') without disclosing behavioral traits such as whether this is a read-only operation, what permissions are needed, how errors are handled, or the format of the returned data. This is inadequate for a tool with no 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 zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without 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 the tool's complexity (a read operation with one parameter) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'searchable attributes' are, what the return value looks like, or how this fits into the broader system (e.g., Meilisearch context), leaving significant gaps for the agent.

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 'Unique identifier of the index'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where 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 'Get the searchable attributes setting' states a clear verb ('Get') and resource ('searchable attributes setting'), but it's vague about what this entails. It doesn't specify whether this retrieves a list, configuration, or status, and it doesn't distinguish from siblings like 'get-filterable-attributes' or 'get-sortable-attributes' beyond the attribute type name.

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., index must exist), exclusions, or related tools like 'update-searchable-attributes' or 'reset-searchable-attributes', leaving the agent to 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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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