Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Mediatype Get

mediatype_get
Read-onlyIdempotent

Retrieves media types from Zabbix to identify notification channels like email, SMS, and webhooks for alert delivery and integrations.

Instructions

Get media types from Zabbix.

Media types define communication channels for sending notifications (email, SMS, webhooks, etc.). Actions use media types to deliver alerts to users and integrations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mediatype_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoDictionary with search criteria like {'name': 'Email'}. Zabbix 5.4 renamed the media type 'description' field to 'name'.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.mediatypeid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
mediatypeidsNoList of media type IDs to get. Omit to return all media types; an empty list matches none.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • changedInput schema / properties / mediatypeids / description
      Previous value: -"List of media type IDs to get. If empty, returns all media types."New value: +"List of media type IDs to get. Omit to return all media types; an empty list matches none."
  2. Changed6 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • changedInput schema / properties / search / description
      Previous value: -"Dictionary with search criteria like {'description': 'email'}."New value: +"Dictionary with search criteria like {'name': 'Email'}. Zabbix 5.4\n    renamed the media type 'description' field to 'name'."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"mediatypeid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds useful domain context about media types being notification channels consumed by actions, but says nothing about result shape, paging or filtering behavior beyond what the schema provides.

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 with the retrieval statement front-loaded. The two explanatory sentences on media types are background rather than invocation guidance, but they are brief and help ground the resource without bloat.

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

Completeness4/5

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

For a simple read-only list tool with 9 well-documented optional parameters and an output schema, the description plus structured fields are sufficient to call it correctly. The only real gap is routing guidance relative to sibling getters.

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 89%, so nearly every parameter is already documented in the schema (limit, offset, search, sortfield, mediatypeids all carry explanations). The description contributes no additional parameter semantics, which is acceptable at this coverage level but not value-adding.

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 ('Get media types from Zabbix') and explains what a media type is, so an agent knows exactly what this retrieves. It does not explicitly distinguish itself from sibling list tools such as action_get, though the resource noun is unambiguous.

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?

The description explains what media types are used for in Zabbix but never says when an agent should call this tool versus the many other *_get siblings, nor any preconditions or exclusions. Usage must be inferred purely from the resource name.

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