Skip to main content
Glama
Sign In
qdrant-llamaindex-mcp-server

qdrant-llamaindex-mcp-server

by azhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

qdrant-delete-documents

Delete multiple documents from a Qdrant collection by specifying their point IDs.

Instructions

Delete multiple documents by their IDs.

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": {
      "point_ids": "<point_ids>",
      "collection_name": "<collection_name>"
    },
    "name": "qdrant-delete-documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
point_idsYesList of point IDs to delete
collection_nameYesThe collection to delete documents from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears full burden but only states the action ('delete'). It does not disclose whether deletion is idempotent, error behavior on missing IDs, or potential side effects, which is insufficient for a destructive operation.

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 short sentence, which is efficient. However, it lacks structure such as front-loading constraints or grouping related info, though it conveys the core action succinctly.

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 no output schema, the description omits return behavior (e.g., confirmation or error). It also fails to mention the batch nature explicitly, which is a key differentiator from sibling tools. Overall, it leaves gaps for an agent to fully understand tool behavior.

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% with descriptions for both parameters. The description adds no extra meaning beyond the schema, so baseline 3 applies. No additional format or context is provided.

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 tool deletes multiple documents by IDs. It distinguishes from sibling 'qdrant-delete-point' (singular) and 'qdrant-delete-collection' (collection level) due to the 'multiple documents' phrasing, though the collection context is implied only via schema.

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 vs alternatives like 'qdrant-delete-point' for single deletion. There is no mention of prerequisites (e.g., collection existence) or scenarios where batch deletion is preferred.

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