Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Usermacro Delete

usermacro_delete
Destructive

Permanently delete host-level macros from Zabbix by macro ID to remove outdated definitions; ensure no items or triggers still reference them to avoid parsing errors.

Instructions

Delete host macros from Zabbix.

Permanently removes host-level macro definitions. Items and triggers using this macro will no longer be able to reference it, potentially causing parsing errors.

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": {
      "hostmacroids": "<hostmacroids>"
    },
    "name": "usermacro_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostmacroidsYesHost macro 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 / hostmacroids / minItems
      Added value: +1
  2. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety bar is low. The description earns credit by adding real downstream context the annotations cannot convey: dependent items and triggers lose the reference and may hit parsing errors, which is exactly the kind of impact an agent needs before calling a destructive tool.

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 tight sentences: the action first, then the blast radius. Nothing is repeated from the annotations or schema and nothing is wasted.

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 no explanation, and the destructive nature plus dependent-object impact is covered. The only missing piece is how to source valid macro IDs (e.g., usermacro_get) before deletion, a small gap for a single-param destructive tool.

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?

There is only one parameter (hostmacroids) with 100% schema coverage, so the schema already carries its meaning. The description adds nothing about format or where these IDs come from, which is the correct baseline when the schema is complete.

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?

States a specific verb and resource ('Delete host macros from Zabbix') and clarifies it is host-level macros, so there's no ambiguity about scope. It does not explicitly distinguish itself from usermacro_get/usermacro_create, but the verb makes the distinction evident.

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?

The consequence sentence implies when to be careful, but there is no explicit guidance on when to delete versus update a macro, or that IDs should first be obtained via usermacro_get. Usage is implied rather than instructed.

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