Skip to main content
Glama
initMAX

Zabbix MCP Server

usermacro_get

Read-only

Retrieve Zabbix user macros globally or for specific hosts/templates to reuse {$MACRO} variables in item keys and triggers; filter by IDs, names, or values.

Instructions

Retrieve user macros. User macros are custom variables ({$MACRO}) that can be defined globally or on individual hosts/templates. They are used in item keys, trigger expressions, and other places to make configuration reusable and environment-specific. Host-level macros override global macros of the same name.

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: automatic (6.2+), hostid, hostmacroid, macro, type, value. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the usermacro 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: hostmacroid, hostid, macro, value. Properties: automatic (6.2+), config (7.4+), description, hostid, hostmacroid, macro, type, value.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, macro, value.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only macros defined on the given hosts.
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: macro (comma-separated 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 usermacro.get parameters, merged into the request as-is. Parameters: globalmacro, groupids, inherited (6.0+). Sub-object selects (value 'extend', 'count' or a list of property names): selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectTemplateGroups (6.2+), selectTemplates. 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.
hostmacroidsNoReturn only host macros with the given IDs.
globalmacroidsNoReturn only global macros with the given IDs.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare this a read-only, open-world operation, so the safety burden is partly lifted. The description adds genuinely useful semantics: that host-level macros override global macros of the same name, which affects how an agent should interpret duplicate results. It does not discuss result volume, default limiting behavior, or permissions.

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?

Three sentences, front-loaded with the action, and the remainder is directly relevant to interpreting macro results. Slightly encyclopedic but no sentence is wasted.

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?

With 15 optional parameters, an output schema, and full schema descriptions, the definition is technically callable. However, nothing tells the agent how filtering axes relate (hostids vs globalmacroids vs filter vs search) or when this tool is the right choice over siblings, which is the main remaining gap.

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 every parameter (limit, filter, output, search, sortfield, extra_params, etc.) is documented in the schema itself. The description adds no parameter-level meaning beyond the domain note about macro scope, so the baseline 3 applies.

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 first sentence gives a clear verb+resource ('Retrieve user macros') and the following sentences explain what a user macro is and how global vs host-level scoping works. This is clear, but it makes no attempt to distinguish the tool from the many sibling *_get retrieval tools it sits alongside.

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 offers domain background but no when-to-use guidance, no prerequisites, and no pointers to alternatives (e.g., host_get for host context or zabbix_raw_api_call mentioned only inside the schema). An agent must infer usage purely from the name and parameters.

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