Skip to main content
Glama
initMAX

Zabbix MCP Server

user_get

Read-only

Retrieve Zabbix user accounts and filter them by user group, media type, ID, or search terms. Return roles, groups, and notification media for access and alerting checks.

Instructions

Retrieve Zabbix user accounts. Each user has a username, role, assigned user groups, and optionally configured media (notification addresses). Use selectMedias, selectUsrgrps, selectRole in the output to include related objects. Filter by usrgrpids to find members of a specific group, or by mediatypeids to find users reachable via a particular notification channel.

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: attempt_clock, attempt_failed, attempt_ip, autologin, autologout, default_maintenance_period (8.0+), lang, name, refresh, roleid (6.0+), rows_per_page, surname, theme, timezone (6.0+), ts_provisioned (6.4+), url, userdirectoryid (6.4+), userid, username (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the user 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: userid, username, name, surname, roleid. Properties: alias (removed in 6.4), attempt_clock, attempt_failed, attempt_ip, autologin, autologout, default_maintenance_period (8.0+), lang, name, provisioned (7.0+), refresh, roleid (6.0+), rows_per_page, surname, theme, timezone (6.0+), ts_provisioned (6.4+), url, userdirectoryid (6.4+), userid, username (6.0+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: attempt_ip, autologout, default_maintenance_period (8.0+), lang, name, refresh, surname, theme, timezone (6.0+), url, username (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
useridsNoReturn only users 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: userid, username (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
usrgrpidsNoReturn only users belonging to these user group IDs.
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 user.get parameters, merged into the request as-is. Parameters: getAccess, mediaids. Sub-object selects (value 'extend', 'count' or a list of property names): selectMedias, selectMediatypes, selectRole (6.0+), selectUsrgrps. 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.
mediatypeidsNoReturn only users that use the given media type IDs for notifications.
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

A3.8/5.0
Behavior3/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. The description adds only that media are optional, which is mild context; it says nothing about pagination behavior, default limits, or the untrusted-data wrapping that the raw_json parameter alludes to. Minimum viable given annotation coverage.

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?

Four sentences, front-loaded with the core verb+resource, then related-object and filtering guidance. Every sentence carries information; there is no filler, though the related-object sentence is a touch redundant with extra_params' schema text.

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

Completeness4/5

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

For a 15-parameter read tool with full schema descriptions and an output schema, the description covers purpose, related-object selection, and the two main filter routes. What remains (raw_json/policy behavior) is handled by schema text, so nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above it by mapping filters to intent (usrgrpids = members of a group, mediatypeids = users reachable on a channel) beyond the schema's bare field listing. Minor wrinkle: it says to pass selectMedias/selectUsrgrps/selectRole 'in the output', though those live under extra_params, which slightly muddies the mapping.

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?

Specific verb + resource: 'Retrieve Zabbix user accounts', plus a concrete inventory of what a user record contains (username, role, groups, media). It is implicitly distinct from usergroup_get/role_get/userdirectory_get siblings, but it never names or contrasts an alternative, so it falls short of the top band.

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

Usage Guidelines4/5

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

Gives actionable usage context: use selectMedias/selectUsrgrps/selectRole to pull related objects, filter by usrgrpids for group membership, or by mediatypeids for notification reachability. There is no explicit when-not-to-use or named alternative to redirect to (e.g. usergroup_get), so it is clear context without exclusions.

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