Skip to main content
Glama
Nam088

mcp-server-db

by Nam088

es_bulk_index

Index multiple documents into a single Elasticsearch index in one request using the _bulk API, with per-document success/failure reporting.

Instructions

Index (create or overwrite) multiple documents into one index in a single request via the Elasticsearch _bulk API (e.g. for seeding test/sample data) — far more efficient than one es_index_doc call per document. Reports per-document success/failure rather than aborting the whole batch on one bad document. Blocked when that connection's own readOnly mode is enabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesIndex name.
documentsYesJSON array of documents to index. Each item may include an "_id" key to set the document id explicitly (removed before indexing); otherwise Elasticsearch auto-generates one. E.g. '[{"_id":"1","title":"foo"},{"title":"bar"}]'
connectionIdNoId of the elasticsearch connection to use, from databases.config.yml. Optional when only one elasticsearch connection is configured.
Behavior4/5

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

Discloses per-document success/failure handling and blocking on readOnly mode. Without annotations, it carries the full burden and provides key behavioral traits, though missing details on error responses.

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?

Two efficient sentences front-load key information. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description hints at result format (per-doc success/failure). Adequate for a bulk indexing tool, but could include response shape.

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 covers 100% of parameter descriptions. The description adds context about _id key handling and optional connectionId, but doesn't significantly surpass schema info. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool indexes multiple documents into one index efficiently via Elasticsearch _bulk API. Mentions use case (seeding test/sample data) and differentiates from single-document tool es_index_doc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly defines when to use (multiple documents, efficiency) versus es_index_doc. Notes blocked when readOnly is enabled. Could further specify when not to use, but current guidance is clear.

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/Nam088/mcp-database-server-v2'

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