Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Item Delete

item_delete
Destructive

Delete one or more Zabbix items by ID to remove them from monitoring and trigger cleanup of associated historical data as configured.

Instructions

Delete items from Zabbix.

Permanently removes one or more items from monitoring. The item's historical data is typically removed as part of cleanup, though this depends on Zabbix configuration.

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": {
      "itemids": "<itemids>"
    },
    "name": "item_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemidsYesItem IDs to delete.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / itemids / minItems
      Added value: +1
  2. First observedv0.5.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description still adds genuine value beyond them by disclosing that deletion is permanent and that historical data removal depends on Zabbix configuration.

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 core action is front-loaded in the first line, with two short supporting sentences. The hedged clause about configuration slightly dilutes the second sentence but still earns its place by warning about irreversible data loss.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully documented in the schema. Destruction consequences are covered; only permission requirements and effects on dependent triggers/entities are absent, which is a minor gap.

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?

Only one parameter exists with 100% schema description coverage, so the schema already documents itemids. The description reinforces that multiple IDs are accepted but adds no format or retrieval details beyond that, making baseline 3 appropriate.

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?

States a specific verb+resource (delete items from Zabbix) and clarifies scope as 'one or more items', which matches the itemids array. It is trivially distinguishable from item_create/item_update/item_get siblings, and there is no competing item-deletion tool to confuse it with.

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

Usage Guidelines3/5

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

Usage is implied by the destructive framing ('Permanently removes'), which signals caution, but there is no explicit guidance on when to delete versus alternatives such as disabling or updating an item, and no stated prerequisites or required permissions.

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