Meilisearch MCP Server

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

Name	Required	Description	Default
`indexUid`	Yes	Unique identifier of the index

Implementation Reference

src/tools/settings-tools.ts:319-328 (handler)

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);
  }
}

src/tools/settings-tools.ts:316-318 (schema)
Input schema for reset-pagination tool: requires indexUid as string.
```
{
  indexUid: z.string().describe("Unique identifier of the index"),
},
```
src/tools/settings-tools.ts:304-308 (registration)
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",
},
```

src/tools/settings-tools.ts:312-330 (registration)

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);
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 10, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It states the tool resets to default, implying a mutation, but doesn't disclose behavioral traits like permissions needed, side effects (e.g., impact on search results), or error handling. It's vague and lacks critical context for safe invocation.

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 front-loads the core action ('reset') and target. It wastes no words and is appropriately sized for a simple tool, making it easy for an agent 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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'default value' means, what happens after reset (e.g., confirmation or error), or how it interacts with other settings. For a mutation tool with siblings, more context is needed to ensure correct usage.

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' well-documented in the schema. The description adds no additional meaning beyond the schema, such as explaining what an index is or how the reset applies. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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'), specifying it sets to 'default value'. It distinguishes from siblings like 'update-pagination' (which modifies) and 'get-pagination' (which retrieves), though it doesn't explicitly name these alternatives. The purpose is specific but could be slightly more distinct.

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 explicit guidance on when to use this tool versus alternatives like 'update-pagination' or 'get-pagination' is provided. The description implies usage for resetting to defaults, but lacks context on prerequisites, timing, or exclusions. It's minimal and doesn't help the agent choose between sibling tools.

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

Deploy Server