Skip to main content
Glama
initMAX

Zabbix MCP Server

template_get

Read-only

Retrieve Zabbix templates to find reusable host configurations, then filter by ID, group, host, or search criteria.

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

TableJSON 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 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+).
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 (comma-separated 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, 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.
with_triggersNoOnly return templates that have triggers.
with_httptestsNoOnly return templates that have web scenarios.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds no behavioral context at all — nothing about pagination defaults, the 19-param filtering model, server targeting, or result size, all of which live only in the schema.

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?

Front-loaded with the core action in three tight sentences and no filler. The remaining sentences are domain background rather than invocation guidance, but they are short and non-redundant.

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

Completeness2/5

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

For a 19-parameter tool with a rich output schema, the description omits everything an agent needs to invoke it correctly: no mention of filtering/searching, no result-limit behavior, no server selection. The template definition is accurate but leaves the operational picture entirely to the schema.

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 the baseline is 3 and the schema already documents limit, filter, search, output, sortfield, and the rest. The description contributes nothing beyond the schema (no mention of limit/search/output interplay), so it neither helps nor harms.

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 ('Retrieve templates') and immediately defines what a template is, including its link/nesting semantics. However, it never distinguishes itself from the many other *_get siblings (templategroup_get, host_get, configuration_export), so an agent gets no differentiation cue.

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?

The description is purely definitional and gives no when-to-use signal, no prerequisites, and no alternative to pick instead (e.g., templategroup_get for groups or templatedashboard_get for dashboards). The conceptual background does not route the agent to or away from this tool.

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