Skip to main content
Glama
initMAX

Zabbix MCP Server

mediatype_get

Read-only

Retrieve Zabbix notification media types to view configured delivery channels (email, SMS, webhook) and diagnose delivery configuration.

Instructions

Retrieve notification media types configured in Zabbix. Media types define how notifications are delivered: Email, SMS, webhook (Slack, PagerDuty, Teams, etc.), or custom scripts. Each media type has its own set of parameters such as SMTP settings, webhook URL, or script path. Use this to list available notification channels or diagnose delivery configuration.

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: access_expires_in (7.4+), access_token (7.4+), access_token_updated (7.4+), attempt_interval, authorization_url (7.4+), client_id (7.4+), client_secret (7.4+), event_menu_name, event_menu_url, exec_params (removed in 6.4), exec_path, gsm_modem, maxattempts, maxsessions, mediatypeid, message_format (7.0+), name, passwd, process_tags, provider (6.4+), redirection_url (7.4+), refresh_token (7.4+), show_event_menu, smtp_authentication, smtp_email, smtp_helo, smtp_port, smtp_security, smtp_server, smtp_verify_host, smtp_verify_peer, status, timeout, token_url (7.4+), tokens_status (7.4+), type, username. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the mediatype 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: mediatypeid, name, type, status. Properties: access_expires_in (7.4+), access_token (7.4+), access_token_updated (7.4+), attempt_interval, authorization_url (7.4+), client_id (7.4+), client_secret (7.4+), content_type (removed in 7.2), description, event_menu_name, event_menu_url, exec_params (removed in 6.4), exec_path, gsm_modem, maxattempts, maxsessions, mediatypeid, message_format (7.0+), name, parameters, passwd, process_tags, provider (6.4+), redirection_url (7.4+), refresh_token (7.4+), script, show_event_menu, smtp_authentication, smtp_email, smtp_helo, smtp_port, smtp_security, smtp_server, smtp_verify_host, smtp_verify_peer, status, timeout, token_url (7.4+), tokens_status (7.4+), type, username.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: access_token (7.4+), attempt_interval, authorization_url (7.4+), client_id (7.4+), client_secret (7.4+), description, event_menu_name, event_menu_url, exec_params (removed in 6.4), exec_path, gsm_modem, name, passwd, redirection_url (7.4+), refresh_token (7.4+), script, smtp_email, smtp_helo, smtp_server, timeout, token_url (7.4+), username.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
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: mediatypeid (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).
extra_paramsNoOther native mediatype.get parameters, merged into the request as-is. Parameters: mediaids, userids. Sub-object selects (value 'extend', 'count' or a list of property names): selectActions (7.0+), selectMessageTemplates, selectUsers. 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 media types with the given IDs.
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.6/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 and reach profile is covered. The description contributes useful conceptual context (what parameters a media type carries) but discloses nothing operationally additional such as result volume, default/projection behavior, or failure modes.

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 purpose before the explanatory middle and the closing usage note. The domain explanation about how media types deliver notifications and carry their own settings earns its place; nothing is redundant, though it is slightly longer than strictly necessary.

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, so return values need not be described, and annotations carry the read-only/open-world safety profile. For a read-only list tool with full schema coverage, the description supplies the missing conceptual layer (what a media type is, why you would query it) and nothing an agent needs to call it correctly is absent.

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 every one of the 13 parameters is already documented in structured data, and the baseline is 3. The description adds no parameter-level guidance (e.g., how filter, search, and output interact) that would exceed the schema.

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 notification media types configured in Zabbix') and adds domain framing that clarifies what a media type actually is (Email, SMS, webhook, custom script). The resource noun is distinct from every sibling *_get tool, though the description never explicitly contrasts itself with them, so it falls just 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 Guidelines3/5

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

'Use this to list available notification channels or diagnose delivery configuration' gives two legitimate use cases, which lifts it above the minimum. However, there are no when-not conditions, no prerequisites, and no named alternatives (e.g., when to prefer searching by name vs. filtering by ID), leaving usage largely implied.

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