Skip to main content
Glama
Sign In
Zabbix MCP Server

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

image_get

Read-only

Retrieve Zabbix images used as map icons or network map backgrounds, with optional metadata-only output to avoid base64 data.

Instructions

Retrieve images stored in Zabbix. Images are used as icons for map elements and as backgrounds for network maps. Two types exist: 1 = icon, 2 = background. By default the image data (base64-encoded) is included in the response; use 'output' to limit returned fields if you only need metadata.

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: imageid, imagetype, name. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the image object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: imageid, name, imagetype. Properties: image (6.4+), imageid, imagetype, name.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
imageidsNoReturn only images with the given IDs.
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.
sortfieldNoSort by one or more of: imageid, name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
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).
extra_paramsNoOther native image.get parameters, merged into the request as-is. Parameters: sysmapids. Sub-object selects (value 'extend', 'count' or a list of property names): select_image. 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.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 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",
+        "sysmapids",
+        "select_image"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "imageid",
+        "imagetype",
+        "name"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "extend",
+      "count"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "image",
+        "imageid",
+        "imagetype",
+        "name"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the image 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: imageid, name, imagetype. Properties: image (6.4+), imageid, imagetype, name."New value: +"Properties of the image object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: imageid, name, imagetype. Properties: image (6.4+), imageid, imagetype, name."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "propertyNames": {
+      "enum": [
+        "name"
+      ]
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "imageid",
+      "name"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "imageid",
+        "name"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: imageid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: imageid, name (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"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "image_getOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.41.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world operation, so the description does not need to carry the full safety burden. It adds useful context about image types and response payload size, but its claim that image data is included by default conflicts with the schema's stated default output of imageid, name, and imagetype.

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 three sentences and front-loads the core purpose. The second and third sentences add useful context about image types and output fields without excessive wandering, though the final sentence contains the problematic default-output claim.

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 13-parameter read-only tool with no output schema, the description does a reasonable job explaining what images are and how they are used. However, it omits guidance on filtering, searching, sorting, and sibling-tool routing, and includes a misleading statement about default output that reduces overall completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all 13 parameters thoroughly. The description's only parameter-specific addition is the claim that image data is returned by default, which contradicts the schema's default output description and could mislead an agent into expecting base64 data when it is not included.

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 states a specific verb and resource: 'Retrieve images stored in Zabbix.' It also clarifies the two image types and their map-related uses, which helps distinguish this from map_get or iconmap_get, though it does not explicitly name those siblings.

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 description implies when to use the tool by explaining that images are icons for map elements and backgrounds for network maps, but it offers no explicit when-to-use versus alternatives guidance. The note about using 'output' is parameter-level guidance rather than tool-selection guidance.

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