Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

update-documents

Modify existing documents in a Meilisearch index by providing updated JSON data and specifying the target index and primary key.

Instructions

Update documents in a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
documentsYesJSON array of documents to update
primaryKeyNoPrimary key for the documents

Implementation Reference

  • The async handler function for the 'update-documents' tool. Parses the input documents JSON string, validates it's an array, optionally sets primaryKey param, performs PUT request to Meilisearch /indexes/{indexUid}/documents endpoint, returns JSON response or formatted error.
    async ({ indexUid, documents, primaryKey }: UpdateDocumentsParams) => {
      try {
        // Parse the documents string to ensure it's valid JSON
        const parsedDocuments = JSON.parse(documents);
        
        // Ensure documents is an array
        if (!Array.isArray(parsedDocuments)) {
          return {
            isError: true,
            content: [{ type: 'text', text: 'Documents must be a JSON array' }],
          };
        }
        
        const params: Record<string, string> = {};
        if (primaryKey) {
          params.primaryKey = primaryKey;
        }
        
        const response = await apiClient.put(`/indexes/${indexUid}/documents`, parsedDocuments, {
          params,
        });
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the 'update-documents' tool: indexUid (required string), documents (required JSON string), primaryKey (optional string).
    {
      indexUid: z.string().describe('Unique identifier of the index'),
      documents: z.string().describe('JSON array of documents to update'),
      primaryKey: z.string().optional().describe('Primary key for the documents'),
    },
  • MCP server.tool() registration call for 'update-documents' tool, including name, description, input schema, and inline handler function.
    server.tool(
      'update-documents',
      'Update documents in a Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index'),
        documents: z.string().describe('JSON array of documents to update'),
        primaryKey: z.string().optional().describe('Primary key for the documents'),
      },
      async ({ indexUid, documents, primaryKey }: UpdateDocumentsParams) => {
        try {
          // Parse the documents string to ensure it's valid JSON
          const parsedDocuments = JSON.parse(documents);
          
          // Ensure documents is an array
          if (!Array.isArray(parsedDocuments)) {
            return {
              isError: true,
              content: [{ type: 'text', text: 'Documents must be a JSON array' }],
            };
          }
          
          const params: Record<string, string> = {};
          if (primaryKey) {
            params.primaryKey = primaryKey;
          }
          
          const response = await apiClient.put(`/indexes/${indexUid}/documents`, parsedDocuments, {
            params,
          });
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • TypeScript interface defining typed parameters for the update-documents handler.
    interface UpdateDocumentsParams {
      indexUid: string;
      documents: string;
      primaryKey?: string;
    }
  • src/index.ts:65-65 (registration)
    Top-level invocation of registerDocumentTools(server) in main server initialization, which registers the document tools including 'update-documents'.
    registerDocumentTools(server);
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action is an update but doesn't clarify whether this overwrites entire documents, merges fields, requires specific permissions, has side effects (e.g., reindexing), or how errors are handled. This is inadequate for a mutation tool with zero 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 wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.

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 mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior (e.g., partial updates, error handling), usage context (vs. siblings), and expected outcomes. Given the complexity of updating documents in a search index, more guidance is needed for effective agent 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%, so parameters are fully documented in the schema. The description adds no additional meaning about parameters (e.g., format of 'documents' as JSON array, what 'primaryKey' does if omitted). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Update') and resource ('documents in a Meilisearch index'), making the purpose immediately understandable. It distinguishes from 'add-documents' by specifying 'update' rather than 'add', though it doesn't explicitly contrast with other document-related siblings like 'delete-documents' or 'get-documents'.

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. The description doesn't mention prerequisites (e.g., existing documents), differentiate from 'add-documents' for new vs. existing records, or explain when to choose this over other document operations like 'delete-documents' or 'get-documents'.

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/devlimelabs/meilisearch-ts-mcp'

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