Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-tasks

Retrieve and filter task information from Meilisearch, including status, type, and index associations for monitoring operations.

Instructions

Get information about tasks with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return
fromNoTask uid from which to start fetching
statusNoStatus of tasks to return
typeNoType of tasks to return
indexUidsNoUIDs of the indexes on which tasks were performed

Implementation Reference

  • Complete registration of the 'get-tasks' MCP tool, including name, description, input schema, and handler function that queries the Meilisearch /tasks endpoint with optional filters.
    server.tool(
      'get-tasks',
      'Get information about tasks with optional filtering',
      {
        limit: z.number().min(0).optional().describe('Maximum number of tasks to return'),
        from: z.number().min(0).optional().describe('Task uid from which to start fetching'),
        status: z.enum(['enqueued', 'processing', 'succeeded', 'failed', 'canceled']).optional().describe('Status of tasks to return'),
        type: z.enum(['indexCreation', 'indexUpdate', 'indexDeletion', 'documentAddition', 'documentUpdate', 'documentDeletion', 'settingsUpdate', 'dumpCreation', 'taskCancelation']).optional().describe('Type of tasks to return'),
        indexUids: z.array(z.string()).optional().describe('UIDs of the indexes on which tasks were performed'),
      },
      async ({ limit, from, status, type, indexUids }) => {
        try {
          const params: Record<string, any> = {};
          if (limit !== undefined) params.limit = limit;
          if (from !== undefined) params.from = from;
          if (status) params.status = status;
          if (type) params.type = type;
          if (indexUids && indexUids.length > 0) params.indexUids = indexUids.join(',');
          
          const response = await apiClient.get('/tasks', { params });
          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 states 'Get information about tasks' which implies a read-only operation, but doesn't disclose behavioral traits like pagination behavior (implied by 'limit' and 'from' parameters), authentication needs, rate limits, or what happens when no filters are applied. The description is minimal and lacks critical operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose ('Get information about tasks') and adds a useful qualifier ('with optional filtering'). However, it could be more structured by explicitly mentioning key parameters or differentiating from siblings.

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 (5 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain return values, error conditions, or how filtering interacts with parameters like 'limit' and 'from'. For a read operation with multiple filters and no structured output, more context is needed to guide effective 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 all parameters well-documented in the schema itself (e.g., 'limit' as 'Maximum number of tasks to return', enums for 'status' and 'type'). The description adds 'optional filtering' which loosely maps to parameters but provides no additional semantic value beyond what the schema already offers, meeting the baseline for high schema coverage.

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 information about tasks with optional filtering' clearly states the verb ('Get') and resource ('tasks'), but it's vague about scope and doesn't differentiate from sibling tools like 'get-task' (singular) or 'list-tasks'. It specifies 'optional filtering' which adds some context but remains generic.

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 'get-task' (singular), 'list-tasks', or 'cancel-tasks'. It mentions 'optional filtering' but doesn't clarify specific use cases or exclusions, leaving the agent to infer usage from parameter names 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