Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

template_get

Read-only

Retrieve Zabbix templates to review reusable items, triggers, graphs, and discovery rules; filter by host, group, ID, name, or properties for audits and automation.

Instructions

Retrieve templates. Templates are reusable sets of items, triggers, graphs, and discovery rules that can be linked to one or more hosts. When a template is linked to a host, all of its entities are automatically applied to that host. Templates belong to template groups and can be nested (linked to other templates).

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: auto_compress (removed in 7.0), custom_interfaces, flags, host, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid (6.0+), vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the template object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: templateid, host, name. Properties: auto_compress (removed in 7.0), custom_interfaces, description, flags, host, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), readme (7.4+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid (6.0+), vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, host, ipmi_password, ipmi_username, name, proxy_address (removed in 7.0), readme (7.4+), tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid (6.0+), vendor_name (6.4+), vendor_version (6.4+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only templates linked to the given hosts.
groupidsNoReturn only templates that belong to the given template/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.
sortfieldNoSort by one or more of: hostid, host, name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
with_itemsNoOnly return templates that have items.
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 templates with the given IDs.
with_graphsNoOnly return templates that have graphs.
extra_paramsNoOther native template.get parameters, merged into the request as-is. Parameters: evaltype, graphids, groupCount, inheritedTags (8.0+), itemids, limitSelects, parentTemplateids, tags, triggerids. 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): selectDashboards (6.0+), selectDiscoveries (deprecated in 7.4, use selectDiscoveryRules), selectDiscoveryRules (7.4+), selectGraphs, selectGroups (removed in 7.2), selectHosts, selectHttpTests, selectInheritedTags (8.0+), selectItems, selectMacros, selectParentTemplates, selectTags, selectTemplateGroups (6.2+), selectTemplates, selectTriggers, selectValueMaps (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_triggersNoOnly return templates that have triggers.
with_httptestsNoOnly return templates that have web scenarios.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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",
      +        "groupCount",
      +        "inheritedTags",
      +        "itemids",
      +        "limitSelects",
      +        "parentTemplateids",
      +        "tags",
      +        "triggerids",
      +        "selectDashboards",
      +        "selectDiscoveries",
      +        "selectDiscoveryRules",
      +        "selectGraphs",
      +        "selectGroups",
      +        "selectHosts",
      +        "selectHttpTests",
      +        "selectInheritedTags",
      +        "selectItems",
      +        "selectMacros",
      +        "selectParentTemplates",
      +        "selectTags",
      +        "selectTemplateGroups",
      +        "selectTemplates",
      +        "selectTriggers",
      +        "selectValueMaps",
      +        "selectApplications",
      +        "selectScreens"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native template.get parameters, merged into the request as-is. Parameters: evaltype, graphids, inheritedTags (8.0+), itemids, limitSelects, parentTemplateids, tags, triggerids. Sub-object selects (value 'extend', 'count' or a list of property names): selectDashboards (6.0+), selectDiscoveries, selectDiscoveryRules (7.4+), selectGraphs, selectGroups (removed in 7.2), selectHosts, selectHttpTests, selectInheritedTags (8.0+), selectItems, selectMacros, selectParentTemplates, selectTags, selectTemplateGroups (6.2+), selectTemplates, selectTriggers, selectValueMaps (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 template.get parameters, merged into the request as-is. Parameters: evaltype, graphids, groupCount, inheritedTags (8.0+), itemids, limitSelects, parentTemplateids, tags, triggerids. 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): selectDashboards (6.0+), selectDiscoveries (deprecated in 7.4, use selectDiscoveryRules), selectDiscoveryRules (7.4+), selectGraphs, selectGroups (removed in 7.2), selectHosts, selectHttpTests, selectInheritedTags (8.0+), selectItems, selectMacros, selectParentTemplates, selectTags, selectTemplateGroups (6.2+), selectTemplates, selectTriggers, selectValueMaps (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": [
      +        "auto_compress",
      +        "custom_interfaces",
      +        "flags",
      +        "host",
      +        "ipmi_authtype",
      +        "ipmi_password",
      +        "ipmi_privilege",
      +        "ipmi_username",
      +        "lastaccess",
      +        "maintenance_from",
      +        "maintenance_status",
      +        "maintenance_type",
      +        "maintenanceid",
      +        "monitored_by",
      +        "name",
      +        "proxy_address",
      +        "proxy_groupid",
      +        "proxy_hostid",
      +        "proxyid",
      +        "status",
      +        "templateid",
      +        "tls_accept",
      +        "tls_connect",
      +        "tls_issuer",
      +        "tls_psk",
      +        "tls_psk_identity",
      +        "tls_subject",
      +        "uuid",
      +        "vendor_name",
      +        "vendor_version",
      +        "wizard_ready"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "auto_compress",
      +        "custom_interfaces",
      +        "description",
      +        "flags",
      +        "host",
      +        "ipmi_authtype",
      +        "ipmi_password",
      +        "ipmi_privilege",
      +        "ipmi_username",
      +        "lastaccess",
      +        "maintenance_from",
      +        "maintenance_status",
      +        "maintenance_type",
      +        "maintenanceid",
      +        "monitored_by",
      +        "name",
      +        "proxy_address",
      +        "proxy_groupid",
      +        "proxy_hostid",
      +        "proxyid",
      +        "readme",
      +        "status",
      +        "templateid",
      +        "tls_accept",
      +        "tls_connect",
      +        "tls_issuer",
      +        "tls_psk",
      +        "tls_psk_identity",
      +        "tls_subject",
      +        "uuid",
      +        "vendor_name",
      +        "vendor_version",
      +        "wizard_ready"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the template 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: templateid, host, name. Properties: auto_compress (removed in 7.0), custom_interfaces, description, flags, host, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), readme (7.4+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid (6.0+), vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+)."New value: +"Properties of the template object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: templateid, host, name. Properties: auto_compress (removed in 7.0), custom_interfaces, description, flags, host, ipmi_authtype, ipmi_password, ipmi_privilege, ipmi_username, lastaccess (removed in 6.2), maintenance_from, maintenance_status, maintenance_type, maintenanceid, monitored_by (7.0+), name, proxy_address (removed in 7.0), proxy_groupid (7.0+), proxy_hostid (removed in 7.0), proxyid (7.0+), readme (7.4+), status, templateid, tls_accept, tls_connect, tls_issuer, tls_psk, tls_psk_identity, tls_subject, uuid (6.0+), vendor_name (6.4+), vendor_version (6.4+), wizard_ready (7.4+)."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "description",
      +        "host",
      +        "ipmi_password",
      +        "ipmi_username",
      +        "name",
      +        "proxy_address",
      +        "readme",
      +        "tls_issuer",
      +        "tls_psk",
      +        "tls_psk_identity",
      +        "tls_subject",
      +        "uuid",
      +        "vendor_name",
      +        "vendor_version"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "hostid",
      +      "host",
      +      "name"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "hostid",
      +        "host",
      +        "name"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: hostid, host, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: hostid, host, 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": "template_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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful domain semantics: templates are reusable entity sets linked to hosts, applied automatically, and nestable, which helps interpret results. However, it does not disclose pagination behavior, default output shape, limits, or other operational traits.

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 short and front-loaded with the core action. The later sentences explain template semantics rather than the tool invocation, but they are relevant context and not excessive.

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?

The schema is very rich, with full descriptions for all 19 parameters, so the description need not repeat parameter details. Yet for a complex retrieval tool with many siblings, the description leaves out usage guidance and behavioral expectations, and there is no output schema to compensate. It is adequate but not complete.

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%, so every parameter, including filter, output, search, and extra_params, is already thoroughly documented in the schema. The description adds no parameter-level meaning beyond that baseline, which is acceptable when the schema does the heavy lifting.

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 and resource: 'Retrieve templates.' It clearly states what the tool returns, but it never distinguishes this tool from similar siblings such as templatedashboard_get or templategroup_get; the remaining sentences are domain background rather than tool-specific scope.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use template_get versus templategroup_get, templatedashboard_get, or host_get. The description gives no conditions, exclusions, or alternative selection hints, so the agent must infer usage from the tool name and schema alone.

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