Skip to main content
Glama
initMAX

Zabbix MCP Server

hostdashboard_get

Read-only

Retrieve dashboards a Zabbix host inherits from linked templates, returning dashboard IDs, names, display settings, and source template per host. Use host IDs and optional page/widget selection.

Instructions

Retrieve the dashboards a host has through its linked templates (Zabbix 7.0+): one record per host and template dashboard with hostid, dashboardid, name, display_period, auto_start and the templateid it comes from. 'hostids' is required. Use selectPages in extra_params for the pages and widgets as resolved for that host. For the template dashboards themselves use templatedashboard_get, for global dashboards dashboard_get. Not documented in the API reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records 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]}. Only these keys are accepted: dashboardid, name, display_period, auto_start, templateid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the hostdashboard 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: hostid, dashboardid, name, templateid. Properties: auto_start, dashboardid, display_period, hostid, name, templateid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Only these keys are accepted: name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsYesReturn the dashboards of these hosts (required).
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, dashboardid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' or 'DESC'.
countOutputNoReturn the count instead of the records.
dashboardidsNoReturn only the given template dashboards.
extra_paramsNoOther native hostdashboard.get parameters, merged into the request as-is. Parameters: groupCount. Sub-object selects (value 'extend', 'count' or a list of property names): selectPages. 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A4.4/5.0
Behavior4/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 non-obvious context the annotations do not: that this endpoint is 'Not documented in the API reference', that records are resolved per host from linked templates, and the exact returned field list. It does not discuss permissions or pagination behavior, so it falls short of the highest bar.

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 operation, then routing, then the required parameter. Efficient overall, though the inline enumeration of return fields (hostid, dashboardid, name, display_period, auto_start, templateid) borders on duplication of the output schema. No wasted preamble.

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

Completeness5/5

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

An output schema exists, annotations carry the read-only/world profile, and the schema is fully described. Given this richness, the description supplies everything else needed: scope, sibling routing, the undocumented-API caveat, and the required hostids. 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.

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 12 parameters thoroughly (filter, search, output, sortfield, extra_params, etc.). The description reinforces that 'hostids' is required and highlights the selectPages usage in extra_params, but adds little beyond what the schema already provides. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (Retrieve) and resource (dashboards a host has through its linked templates), and immediately distinguishes the result shape: one record per host and template dashboard with the specific fields returned. It also names the sibling tools it is NOT (templatedashboard_get, dashboard_get), so an agent can differentiate without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing is given: 'use selectPages in extra_params for the pages and widgets as resolved for that host', 'for the template dashboards themselves use templatedashboard_get, for global dashboards dashboard_get'. Both the use case and the alternatives are stated concretely, with the required 'hostids' called out.

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