delete_topic
Deletes 1–1000 Kafka topics after previewing message and partition counts, requiring explicit confirmation and data-loss acknowledgement before destructive changes.
Instructions
Delete 1 to 1000 Kafka topics in one call through items. Deleting one topic is an items array of length one.
This is the most destructive tool here. Deleting a topic destroys every message in it, and Kafka has no undo: recreating the topic does not bring the data back. Any consumer group reading it breaks.
Nothing is deleted unless confirm is true; otherwise the response reports, per topic, how many messages would be destroyed, how many partitions it had, and which consumer groups had committed offsets for it. A topic that still holds messages also requires acknowledge_data_loss on its item, so destroying data is never a single unconsidered call.
One confirm covers the whole batch, and deletion is not atomic: topics deleted before a later item failed stay deleted. Results follow items order, each carrying index with result or error. Internal topics are refused. Requires Kafka DELETE permission.
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": {
"items": "<items>"
},
"name": "delete_topic"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | The topics to delete, 1 to 1000 of them. Deleting one topic is an array of length one. Naming the same topic twice is refused before anything is deleted. | |
| confirm | No | Optional. When false or omitted, nothing is deleted and the response describes what each deletion would destroy. Must be true to actually delete. One confirm covers the whole batch. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| atomic | Yes | ||
| failed | Yes | ||
| applied | Yes | ||
| results | Yes | ||
| succeeded | Yes |