Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

hostgroup_get

Read-only

Retrieve Zabbix host groups to organize hosts, control access permissions, and filter related hosts, items, and triggers by group.

Instructions

Retrieve host groups. Host groups are used to logically organize hosts and to control access permissions. Every host must belong to at least one host group. Groups can also be used to filter when retrieving hosts, items, triggers, etc.

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: flags, groupid, internal (removed in 6.2), name, uuid (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the hostgroup object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: groupid, name. Properties: flags, groupid, internal (removed in 6.2), name, uuid (6.0+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only host groups that contain the given hosts.
groupidsNoReturn only host groups 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: groupid, name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
with_hostsNoOnly return host groups that contain at least one host.
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 hostgroup.get parameters, merged into the request as-is. Parameters: graphids, groupCount (removed in 6.2), limitSelects, maintenanceids, monitored_hosts (removed in 7.2), real_hosts (removed in 7.2), templated_hosts (removed in 6.2), templateids (removed in 6.2), triggerids, with_graph_prototypes, with_graphs, with_hosts_and_templates (removed in 6.2), with_httptests, with_item_prototypes, with_items, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items, with_triggers. Switches (true turns one on, false is the same as leaving it out): groupCount, monitored_hosts, real_hosts, templated_hosts, with_graph_prototypes, with_graphs, with_hosts_and_templates, with_httptests, with_item_prototypes, with_items, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items, with_triggers. groupCount (removed in 6.2) 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): selectDiscoveryData (7.4+), selectDiscoveryRule (removed in 7.0), selectDiscoveryRules (7.0+), selectGroupDiscoveries (7.0+, deprecated in 7.4, use selectDiscoveryData), selectGroupDiscovery (removed in 7.0), selectHostPrototype (removed in 7.0), selectHostPrototypes (7.0+), selectHosts, selectTemplates (removed in 6.2). 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_monitored_hostsNoOnly return host groups that contain at least one monitored (enabled) host.
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",
      +        "graphids",
      +        "groupCount",
      +        "limitSelects",
      +        "maintenanceids",
      +        "monitored_hosts",
      +        "real_hosts",
      +        "templated_hosts",
      +        "templateids",
      +        "triggerids",
      +        "with_graph_prototypes",
      +        "with_graphs",
      +        "with_hosts_and_templates",
      +        "with_httptests",
      +        "with_item_prototypes",
      +        "with_items",
      +        "with_monitored_httptests",
      +        "with_monitored_items",
      +        "with_monitored_triggers",
      +        "with_simple_graph_item_prototypes",
      +        "with_simple_graph_items",
      +        "with_triggers",
      +        "with_applications",
      +        "selectDiscoveryData",
      +        "selectDiscoveryRule",
      +        "selectDiscoveryRules",
      +        "selectGroupDiscoveries",
      +        "selectGroupDiscovery",
      +        "selectHostPrototype",
      +        "selectHostPrototypes",
      +        "selectHosts",
      +        "selectTemplates"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native hostgroup.get parameters, merged into the request as-is. Parameters: graphids, limitSelects, maintenanceids, monitored_hosts (removed in 7.2), real_hosts (removed in 7.2), templated_hosts (removed in 6.2), templateids (removed in 6.2), triggerids, with_graph_prototypes, with_graphs, with_hosts_and_templates (removed in 6.2), with_httptests, with_item_prototypes, with_items, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items, with_triggers. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule (removed in 7.0), selectDiscoveryRules (7.0+), selectGroupDiscoveries (7.0+), selectGroupDiscovery (removed in 7.0), selectHostPrototypes (7.0+), selectHosts, selectTemplates (removed in 6.2). 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 hostgroup.get parameters, merged into the request as-is. Parameters: graphids, groupCount (removed in 6.2), limitSelects, maintenanceids, monitored_hosts (removed in 7.2), real_hosts (removed in 7.2), templated_hosts (removed in 6.2), templateids (removed in 6.2), triggerids, with_graph_prototypes, with_graphs, with_hosts_and_templates (removed in 6.2), with_httptests, with_item_prototypes, with_items, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items, with_triggers. Switches (true turns one on, false is the same as leaving it out): groupCount, monitored_hosts, real_hosts, templated_hosts, with_graph_prototypes, with_graphs, with_hosts_and_templates, with_httptests, with_item_prototypes, with_items, with_monitored_httptests, with_monitored_items, with_monitored_triggers, with_simple_graph_item_prototypes, with_simple_graph_items, with_triggers. groupCount (removed in 6.2) 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): selectDiscoveryData (7.4+), selectDiscoveryRule (removed in 7.0), selectDiscoveryRules (7.0+), selectGroupDiscoveries (7.0+, deprecated in 7.4, use selectDiscoveryData), selectGroupDiscovery (removed in 7.0), selectHostPrototype (removed in 7.0), selectHostPrototypes (7.0+), selectHosts, selectTemplates (removed in 6.2). 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": [
      +        "flags",
      +        "groupid",
      +        "internal",
      +        "name",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "flags",
      +        "groupid",
      +        "internal",
      +        "name",
      +        "uuid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the hostgroup 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: groupid, name. Properties: flags, groupid, internal (removed in 6.2), name, uuid (6.0+)."New value: +"Properties of the hostgroup object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: groupid, name. Properties: flags, groupid, internal (removed in 6.2), name, uuid (6.0+)."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "name",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "groupid",
      +      "name"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "groupid",
      +        "name"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: groupid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: groupid, 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": "hostgroup_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.2/5.0
Behavior2/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 covered. The description adds no behavior beyond that: nothing about default result fields (groupid, name), pagination/limit behavior, count mode, or the fact that responses are wrapped in a security preamble unless raw_json is set. Its content is domain background rather than operational behavior.

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 short sentences, front-loaded with the action before the background definition, and no repetition. The explanatory sentences are contextual rather than wasteful, though they could have been spent on routing or return-shape information instead.

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 16-parameter read tool with no output schema, the description is thin: it says nothing about the shape of returned host group objects, the default field selection, or how results differ between normal, count, and extended modes. The exhaustive schema compensates for parameter-level gaps, but an agent still lacks a description-level picture of what comes back.

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 one of the 16 parameters carries its own detailed documentation (including the raw_json policy warning and extra_params allowlist). The description contributes nothing about parameters, 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?

"Retrieve host groups" gives a clear verb and resource, and the follow-on sentences define what a host group is (logical host organization plus access control). It does not, however, distinguish this tool from the closely related sibling hostgroup_overview_get or from host_get, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: the note that groups 'can also be used to filter when retrieving hosts, items, triggers' hints at how group IDs are consumed elsewhere, but there is no explicit when-to-use, when-not-to-use, or named alternative. With hostgroup_overview_get present in the sibling list, this omission is a real gap.

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