Skip to main content
Glama
Octodet

octodet-elasticsearch-mcp

update_document

Modify specific fields in an existing document within an Elasticsearch index by providing the index name, document ID, and updated content.

Instructions

Update an existing document in a specific Elasticsearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentYesPartial document body to update (fields to change)
idYesDocument ID to update
indexYesName of the Elasticsearch index

Implementation Reference

  • MCP tool handler for 'update_document' that validates input, calls the Elasticsearch service, and formats success/error responses.
    async ({ index, id, document }) => {
      try {
        await esService.updateDocument(index, id, document);
        return {
          content: [
            {
              type: "text",
              text: `Document with ID '${id}' updated in index '${index}'.`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error updating document: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining input parameters for the update_document tool: index (string), id (string), document (record).
    {
      index: z
        .string()
        .trim()
        .min(1, "Index name is required")
        .describe("Name of the Elasticsearch index"),
      id: z
        .string()
        .min(1, "Document ID is required")
        .describe("Document ID to update"),
      document: z
        .record(z.any())
        .describe("Partial document body to update (fields to change)"),
    },
  • src/index.ts:460-501 (registration)
    Registration of the 'update_document' tool on the MCP server using server.tool(), including name, description, schema, and handler.
    server.tool(
      "update_document",
      "Update an existing document in a specific Elasticsearch index",
      {
        index: z
          .string()
          .trim()
          .min(1, "Index name is required")
          .describe("Name of the Elasticsearch index"),
        id: z
          .string()
          .min(1, "Document ID is required")
          .describe("Document ID to update"),
        document: z
          .record(z.any())
          .describe("Partial document body to update (fields to change)"),
      },
      async ({ index, id, document }) => {
        try {
          await esService.updateDocument(index, id, document);
          return {
            content: [
              {
                type: "text",
                text: `Document with ID '${id}' updated in index '${index}'.`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error updating document: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      }
    );
  • Helper function in ElasticsearchService that executes the actual Elasticsearch client update operation.
    async updateDocument(index: string, id: string, document: any): Promise<any> {
      return await this.client.update({
        index,
        id,
        doc: document,
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether it's idempotent, how conflicts are handled, what happens on partial updates, or any rate limits. This leaves significant behavioral gaps for a mutation tool.

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 states the core purpose without unnecessary words. It's appropriately sized for a tool with good schema documentation and gets straight to the point.

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 doesn't explain what the tool returns, error conditions, or important behavioral aspects. Given the complexity of document updates in Elasticsearch and the rich sibling toolset, more context is needed for 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%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain the relationship between parameters or provide usage examples. This meets the baseline for high schema coverage.

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 verb 'update' and the resource 'existing document in a specific Elasticsearch index', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'update_by_query' or 'add_document', which would require more specific scope information.

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 'update_by_query' or 'add_document'. It mentions 'existing document' but doesn't clarify prerequisites, error conditions, or typical use cases compared to other update operations.

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

Related 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/Octodet/elasticsearch-mcp'

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