Skip to main content
Glama
initMAX

Zabbix MCP Server

graph_get

Read-only

Retrieve Zabbix graphs to view item data trends over time. Filter by hosts, host groups, templates, or graph IDs to find the exact visual representation you need.

Instructions

Retrieve graphs. Graphs provide visual representations of item data over time. Each graph contains one or more graph items (data series) that reference Zabbix items. Graphs belong to hosts or templates.

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: flags, graphid, graphtype, height, name, percent_left, percent_right, show_3d, show_legend, show_triggers, show_work_period, templateid, uuid (6.0+), width, yaxismax, yaxismin, ymax_itemid, ymax_type, ymin_itemid, ymin_type. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the graph 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: graphid, name. Properties: flags, graphid, graphtype, height, name, percent_left, percent_right, show_3d, show_legend, show_triggers, show_work_period, templateid, uuid (6.0+), width, yaxismax, yaxismin, ymax_itemid, ymax_type, ymin_itemid, ymin_type.
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 graphs that belong to the given hosts.
graphidsNoReturn only graphs with the given IDs.
groupidsNoReturn only graphs that belong to hosts in the given host groups.
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: graphid, name, graphtype (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).
templateidsNoReturn only graphs that belong to the given templates.
extra_paramsNoOther native graph.get parameters, merged into the request as-is. Parameters: expandName, inherited, itemids, templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphDiscovery, selectGraphItems, selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts, selectItems, 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.
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 readOnlyHint=true and openWorldHint=true, so safety is covered. The description contributes the object model (graphs contain graph items; they hang off hosts or templates), which helps the agent reason about the filter parameters, but it discloses nothing about pagination, default limits, or result volume for what is a potentially large listing operation.

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 action, and no redundancy. The three domain sentences are informative rather than padding, though two of them are arguably background an agent could do without when merely selecting the tool.

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 16 parameters, an output schema handling returns, and annotations covering safety, the description only needs to orient the agent — but for a tool this broad it stays at the conceptual level and gives no sense of how to scope a query or what the practical result shape/size is. Minimum viable, with clear gaps.

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% across all 16 parameters, so the schema already carries full parameter semantics. The description adds nothing parameter-specific (no mention of graphids, hostids, filter, search, or limit), so the baseline 3 is appropriate.

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?

States a specific verb and resource ("Retrieve graphs") and adds real domain substance: graphs are visual representations of item data over time, composed of graph items that reference Zabbix items, and belonging to hosts or templates. It does not, however, distinguish itself from obvious siblings such as graphitem_get or graphprototype_get, so an agent must infer the boundary.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives (graphitem_get for data series, graph_render for images, graphprototype_get for template-level prototypes). The domain sentence implies scope but never says when this tool is the right choice.

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