Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

user_get

Read-only

Retrieve Zabbix user accounts with roles, groups, and notification media, and filter by user group or media type to find specific users or counts.

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

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 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, alias (removed in 6.4) (a list 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: current (8.0+), getAccess, mediaids. Switches (true turns one on, false is the same as leaving it out): getAccess. 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.

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",
      +        "current",
      +        "getAccess",
      +        "mediaids",
      +        "selectMedias",
      +        "selectMediatypes",
      +        "selectRole",
      +        "selectUsrgrps"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other 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."New value: +"Other native user.get parameters, merged into the request as-is. Parameters: current (8.0+), getAccess, mediaids. Switches (true turns one on, false is the same as leaving it out): getAccess. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "attempt_clock",
      +        "attempt_failed",
      +        "attempt_ip",
      +        "autologin",
      +        "autologout",
      +        "default_maintenance_period",
      +        "lang",
      +        "name",
      +        "refresh",
      +        "roleid",
      +        "rows_per_page",
      +        "surname",
      +        "theme",
      +        "timezone",
      +        "ts_provisioned",
      +        "url",
      +        "userdirectoryid",
      +        "userid",
      +        "username",
      +        "type"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "alias",
      +        "attempt_clock",
      +        "attempt_failed",
      +        "attempt_ip",
      +        "autologin",
      +        "autologout",
      +        "default_maintenance_period",
      +        "lang",
      +        "name",
      +        "provisioned",
      +        "refresh",
      +        "roleid",
      +        "rows_per_page",
      +        "surname",
      +        "theme",
      +        "timezone",
      +        "ts_provisioned",
      +        "url",
      +        "userdirectoryid",
      +        "userid",
      +        "username",
      +        "type"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties 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+)."New value: +"Properties of the user object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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+)."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "attempt_ip",
      +        "autologout",
      +        "default_maintenance_period",
      +        "lang",
      +        "name",
      +        "refresh",
      +        "surname",
      +        "theme",
      +        "timezone",
      +        "url",
      +        "username"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "userid",
      +      "username",
      +      "alias"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "userid",
      +        "username",
      +        "alias"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: userid, username (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: userid, username, alias (removed in 6.4) (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": "user_getOutput",
      -  "type": "object"
      -}New value: +null
  2. 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=false, so the safety profile is carried by structured data. The description adds the shape of returned records and the opt-in nature of related objects, but says nothing about default result limits, pagination behavior, permission requirements for reading users, or the raw_json/disclaimer framing covered elsewhere in the schema. Useful but not rich behavioral context.

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 verb and resource, then object shape, then parameter routing. No filler, though the middle sentences restate some schema-level detail that could have been compressed.

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 15-parameter, no-required-params, no-output-schema tool, the description covers the core object shape but omits default behavior when no filters are supplied, how limit/countOutput interact, and the default output field set. These gaps are partly filled by schema descriptions, but an agent still has to read the schema to know what a bare call returns.

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 the parameters the description highlights (usrgrpids, mediatypeids, selectMedias/selectUsrgrps/selectRole) are already documented in their own schema entries. The description therefore adds emphasis and a usage frame rather than new meaning, so the baseline 3 for a fully documented schema is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and resource ('Retrieve Zabbix user accounts') and immediately describes the object shape (username, role, groups, media), which cleanly separates it from siblings such as usergroup_get, role_get and userdirectory_get. An agent can tell what this returns without opening the schema.

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?

It gives concrete routing guidance within the tool: use selectMedias/selectUsrgrps/selectRole to pull related objects, usrgrpids for group membership, mediatypeids for notification-channel reachability. It does not name an alternative tool or state when NOT to use this one (e.g. versus usergroup_get or user_checkauthentication), so it stops short of full when/when-not coverage.

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