Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-pagination

Reset pagination settings to default values for a Meilisearch index to restore standard search result display.

Instructions

Reset the pagination setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Shared handler function for all reset-* tools, including reset-pagination. It deletes the specific settings endpoint (/indexes/{indexUid}/settings/pagination) via apiClient to reset to default values.
    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 reset-pagination tool: requires indexUid as string.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration entry in resetSettingsTools array defining the name, endpoint, and description for the reset-pagination tool.
    {
      name: "reset-pagination",
      endpoint: "pagination",
      description: "Reset the pagination setting to its default value",
    },
  • Loop that dynamically registers the reset-pagination tool (and others) on the MCP server using server.tool() with the configuration from the array.
    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 registerSettingsTools(server) which registers all settings tools including reset-pagination.
    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 states the tool resets settings, implying a mutation, but doesn't mention potential side effects (e.g., impact on search results), permissions required, or error conditions. This leaves significant gaps in understanding how the tool behaves beyond the basic action.

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, clear sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and efficient, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is minimal but covers the basic action. It lacks details on behavioral aspects like side effects or return values, which are important given the context. However, the simplicity of the tool (one parameter, straightforward reset) makes this somewhat adequate but with clear gaps.

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 as 'Unique identifier of the index'. The description doesn't add any extra meaning beyond this, such as explaining what an index is or providing examples. 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 ('pagination setting to its default value'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'update-pagination' or 'get-pagination', which would require mentioning it's specifically for reverting to defaults rather than modifying or retrieving settings.

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 like 'update-pagination' or 'get-pagination'. The description lacks context about prerequisites, such as needing an existing index or after changes to pagination settings, leaving usage unclear.

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