Skip to main content
Glama
Sign In
Elasticsearch MCP Server

Elasticsearch MCP Server

by jesee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

es_delete_document

Delete a document from an Elasticsearch index by specifying the index name and document ID.

Instructions

Delete a document

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>",
      "id": "<id>"
    },
    "name": "es_delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument ID
indexYesIndex name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention that deletion is irreversible, may require permissions, or what happens to related data. The description is too sparse.

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

Conciseness3/5

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

The three-word description is extremely concise but at the cost of missing crucial details. It is front-loaded but under-specified for an agent to use confidently.

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 lack of output schema and annotations, and the simplicity of the operation, the description is insufficient. It does not explain return values, error cases, or how the deletion integrates with the index lifecycle.

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 coverage is 100% as both parameters have descriptions in the schema. The description 'Delete a document' adds no additional meaning beyond what the schema already provides, so baseline 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 (delete) and resource (document). The verb 'Delete' and noun 'document' are specific and distinguish from sibling tools like es_get_document or es_update_document, though it does not explicitly differentiate.

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 updating or indexing. There is no mention of prerequisites (e.g., document must exist) or conditions for use.

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

Deploy Server

Other Tools