Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

item_get

Read-only

Retrieve Zabbix items to find host metrics such as CPU, memory, and disk usage, and filter results by host, group, template, or trigger.

Instructions

Retrieve items. Items are the individual data collection points in Zabbix - each item gathers a specific metric from a host (CPU usage, memory, disk space, etc.). Items belong to hosts and are bound to a host interface. Trigger expressions reference items by their keys to define alerting conditions.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: allow_traps, authtype, delay, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), evaltype, flags, follow_redirects, formula, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, password, post_type, privatekey, publickey, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the item object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: itemid, hostid, name, key_, status, value_type. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: delay, description, error, formula, granularity (8.0+), history, http_proxy, ipmi_sensor, jmx_endpoint, key_, lifetime, logtimefmt, lookback_limit (8.0+), name, name_resolved (7.0+), params, password, posts, privatekey, publickey, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status_codes, time_shift (8.0+), timeout, trapper_hosts, trends, units, url, username, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only items that belong to the given hosts.
itemidsNoReturn only items with the given IDs.
groupidsNoReturn only items that belong to hosts in the given host groups.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
webitemsNoInclude web items (items created by web scenarios) in the result.
sortfieldNoSort by one or more of: itemid, name, key_, delay, history, trends, type, status (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
triggeridsNoReturn only items used in the given triggers.
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
templateidsNoReturn only items that belong to the given templates.
extra_paramsNoOther native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, groupCount, host, inherited, inheritedTags (8.0+), interfaceids, limitSelects, monitored, proxyids, tags (6.0+), templated. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery (deprecated in 7.4, use selectDiscoveryData), selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
with_triggersNotrue = only items used in at least one trigger, false = only items used in no trigger. Omit it for both.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "evaltype",
      +        "graphids",
      +        "group",
      +        "groupCount",
      +        "host",
      +        "inherited",
      +        "inheritedTags",
      +        "interfaceids",
      +        "limitSelects",
      +        "monitored",
      +        "proxyids",
      +        "tags",
      +        "templated",
      +        "application",
      +        "applicationids",
      +        "selectDiscoveryData",
      +        "selectDiscoveryRule",
      +        "selectGraphs",
      +        "selectHosts",
      +        "selectInheritedTags",
      +        "selectInterfaces",
      +        "selectItemDiscovery",
      +        "selectPreprocessing",
      +        "selectTags",
      +        "selectTriggers",
      +        "selectValueMap",
      +        "selectApplications"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, host, inherited, inheritedTags (8.0+), interfaceids, limitSelects, monitored, proxyids, tags (6.0+), templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery, selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call."New value: +"Other native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, groupCount, host, inherited, inheritedTags (8.0+), interfaceids, limitSelects, monitored, proxyids, tags (6.0+), templated. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery (deprecated in 7.4, use selectDiscoveryData), selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "allow_traps",
      +        "authtype",
      +        "delay",
      +        "enabled_lifetime",
      +        "enabled_lifetime_type",
      +        "evaltype",
      +        "flags",
      +        "follow_redirects",
      +        "formula",
      +        "granularity",
      +        "history",
      +        "hostid",
      +        "http_proxy",
      +        "interfaceid",
      +        "inventory_link",
      +        "ipmi_sensor",
      +        "itemid",
      +        "jmx_endpoint",
      +        "key_",
      +        "lifetime",
      +        "lifetime_type",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "master_itemid",
      +        "name",
      +        "name_resolved",
      +        "output_format",
      +        "password",
      +        "post_type",
      +        "privatekey",
      +        "publickey",
      +        "request_method",
      +        "retrieve_mode",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "state",
      +        "status",
      +        "status_codes",
      +        "templateid",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "type",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid",
      +        "value_type",
      +        "valuemapid",
      +        "verify_host",
      +        "verify_peer"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "allow_traps",
      +        "authtype",
      +        "delay",
      +        "description",
      +        "enabled_lifetime",
      +        "enabled_lifetime_type",
      +        "error",
      +        "evaltype",
      +        "flags",
      +        "follow_redirects",
      +        "formula",
      +        "granularity",
      +        "headers",
      +        "history",
      +        "hostid",
      +        "http_proxy",
      +        "interfaceid",
      +        "inventory_link",
      +        "ipmi_sensor",
      +        "itemid",
      +        "jmx_endpoint",
      +        "key_",
      +        "lastclock",
      +        "lastns",
      +        "lastvalue",
      +        "lifetime",
      +        "lifetime_type",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "master_itemid",
      +        "name",
      +        "name_resolved",
      +        "output_format",
      +        "parameters",
      +        "params",
      +        "password",
      +        "post_type",
      +        "posts",
      +        "prevvalue",
      +        "privatekey",
      +        "publickey",
      +        "query",
      +        "query_fields",
      +        "request_method",
      +        "retrieve_mode",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "state",
      +        "status",
      +        "status_codes",
      +        "templateid",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "type",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid",
      +        "value_type",
      +        "valuemapid",
      +        "verify_host",
      +        "verify_peer"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the item object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: itemid, hostid, name, key_, status, value_type. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer."New value: +"Properties of the item object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: itemid, hostid, name, key_, status, value_type. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "delay",
      +        "description",
      +        "error",
      +        "formula",
      +        "granularity",
      +        "history",
      +        "http_proxy",
      +        "ipmi_sensor",
      +        "jmx_endpoint",
      +        "key_",
      +        "lifetime",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "name",
      +        "name_resolved",
      +        "params",
      +        "password",
      +        "posts",
      +        "privatekey",
      +        "publickey",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "status_codes",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "itemid",
      +      "name",
      +      "key_",
      +      "delay",
      +      "history",
      +      "trends",
      +      "type",
      +      "status"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "itemid",
      +        "name",
      +        "key_",
      +        "delay",
      +        "history",
      +        "trends",
      +        "type",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: itemid, name, key_, delay, history, trends, type, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: itemid, name, key_, delay, history, trends, type, status (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / with_triggers / description
      Previous value: -"Only return items that are used in at least one trigger."New value: +"true = only items used in at least one trigger, false = only items used in no trigger. Omit it for both."
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "item_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds domain context (host/interface binding, trigger key references) but says nothing beyond the schema about result volume, pagination, default field set, or count behavior, so it does little extra behavioral work.

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?

It is short and front-loaded with the action and resource, and the model definition is a useful primer for interpreting the returned fields. The middle sentences are mildly encyclopedic and could be trimmed for an agent that already knows the Zabbix data model.

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

Completeness3/5

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

For a read tool with 19 optional parameters and no output schema, the description covers the conceptual domain adequately and the schema carries the mechanics. It omits anything about result crowding, defaults, or how the many filter/search/output options interact, which an agent must discover from the schema alone.

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 description coverage is 100% and the individual parameters (filter, search, output, extra_params, raw_json) are documented in detail in the schema itself. The description adds no parameter-level meaning, so the baseline of 3 applies for a high-coverage schema.

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 opens with a specific verb+resource ("Retrieve items") and immediately defines what an item is in Zabbix, which tells an agent this returns monitoring item definitions rather than history or trigger data. It never names its nearest siblings (itemprototype_get, history_get, trigger_get) to draw the line explicitly, so it is clear but not fully differentiated.

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 only implied by the domain explanation: items belong to hosts, are bound to interfaces, and are referenced by trigger expressions, which hints at filtering by hostid/triggerids. There is no explicit when-to-use guidance, no when-not-to-use, and no pointer to alternatives such as itemprototype_get or history_get for value data.

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