Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

alert_get

Read-only

Retrieve Zabbix alert log entries to inspect notification and remote-command delivery status, retries, errors, and message bodies, helping diagnose why notifications were not received.

Instructions

Retrieve the alert log -- a read-only record of every notification and remote command Zabbix has executed as a result of actions. Each alert entry contains delivery status, retry count, error text (if failed), and the message body. Use time_from/time_till to scope by time window. Great for diagnosing 'why didn't I get notified?' issues. The newest alerts come first unless a sort is given.

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: acknowledgeid, actionid, alertid, alerttype, clock, error, esc_step, eventid, mediatypeid, p_eventid, retries, sendto, status, subject, userid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the alert object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: alertid, actionid, mediatypeid, status, clock. Properties: acknowledgeid, actionid, alertid, alerttype, clock, error, esc_step, eventid, mediatypeid, message, p_eventid, retries, sendto, status, subject, userid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: error, message, sendto, subject.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only alerts for the given host IDs.
alertidsNoReturn only alerts with the given IDs.
groupidsNoReturn only alerts for hosts belonging to these host group 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.
actionidsNoReturn only alerts generated by the given action IDs.
sortfieldNoSort by one or more of: alertid, clock, eventid, mediatypeid, sendto, status (a list for several; pair with 'sortorder'). No other property is sortable. When omitted, the result is sorted by alertid with the newest first.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending). 'DESC' while 'sortfield' is omitted (newest first); 'ASC' alone returns the oldest first.
time_fromNoReturn only alerts generated after this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call) (inclusive). Useful for auditing recent notification delivery.
time_tillNoReturn only alerts generated before this time (Unix timestamp, ISO 8601 date-time such as 2026-04-01T08:00:00Z, or a relative time such as now-1h, now/d or now-7d/d; a value without a zone is read in the zone resolved for the call) (inclusive).
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 alert.get parameters, merged into the request as-is. Parameters: eventids, eventobject, eventsource, groupCount, mediatypeids, objectids, userids. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount 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): selectHosts, selectMediatypes, 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.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 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",
      +        "eventids",
      +        "eventobject",
      +        "eventsource",
      +        "groupCount",
      +        "mediatypeids",
      +        "objectids",
      +        "userids",
      +        "selectHosts",
      +        "selectMediatypes",
      +        "selectUsers"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native alert.get parameters, merged into the request as-is. Parameters: eventids, eventobject, eventsource, mediatypeids, objectids, userids. Sub-object selects (value 'extend', 'count' or a list of property names): selectHosts, selectMediatypes, 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."New value: +"Other native alert.get parameters, merged into the request as-is. Parameters: eventids, eventobject, eventsource, groupCount, mediatypeids, objectids, userids. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount 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): selectHosts, selectMediatypes, 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "acknowledgeid",
      +        "actionid",
      +        "alertid",
      +        "alerttype",
      +        "clock",
      +        "error",
      +        "esc_step",
      +        "eventid",
      +        "mediatypeid",
      +        "p_eventid",
      +        "retries",
      +        "sendto",
      +        "status",
      +        "subject",
      +        "userid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "acknowledgeid",
      +        "actionid",
      +        "alertid",
      +        "alerttype",
      +        "clock",
      +        "error",
      +        "esc_step",
      +        "eventid",
      +        "mediatypeid",
      +        "message",
      +        "p_eventid",
      +        "retries",
      +        "sendto",
      +        "status",
      +        "subject",
      +        "userid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the alert 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: alertid, actionid, mediatypeid, status, clock. Properties: acknowledgeid, actionid, alertid, alerttype, clock, error, esc_step, eventid, mediatypeid, message, p_eventid, retries, sendto, status, subject, userid."New value: +"Properties of the alert object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: alertid, actionid, mediatypeid, status, clock. Properties: acknowledgeid, actionid, alertid, alerttype, clock, error, esc_step, eventid, mediatypeid, message, p_eventid, retries, sendto, status, subject, userid."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "error",
      +        "message",
      +        "sendto",
      +        "subject"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "alertid",
      +      "clock",
      +      "eventid",
      +      "mediatypeid",
      +      "sendto",
      +      "status"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "alertid",
      +        "clock",
      +        "eventid",
      +        "mediatypeid",
      +        "sendto",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: alertid, clock, eventid, mediatypeid, sendto, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: alertid, clock, eventid, mediatypeid, sendto, status (a list for several; pair with 'sortorder'). No other property is sortable. When omitted, the result is sorted by alertid with the newest first."
    • 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"
      +  }
      +]
    • changedInput schema / properties / sortorder / description
      Previous value: -"Sort order: 'ASC' (ascending) or 'DESC' (descending)."New value: +"Sort order: 'ASC' (ascending) or 'DESC' (descending). 'DESC' while 'sortfield' is omitted (newest first); 'ASC' alone returns the oldest first."
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "alert_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description reinforces it with 'read-only record' and adds real behavioral value by describing what each entry contains (delivery status, retry count, error text, message body) and the default ordering (newest first unless a sort is given). It omits the raw_json prompt-injection tradeoff, but that is documented thoroughly in the schema rather than being the description's burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the resource definition before the use case and sort caveat. Every sentence contributes information about the resource, its contents, or how to scope it; nothing is redundant padding.

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 an 18-parameter, zero-required read tool with no output schema, the description does well by enumerating the fields each alert entry returns, partially substituting for a missing output schema. The main gap is that it says nothing about the raw_json security preamble or result-size behavior, both of which are only discoverable in the schema.

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 18 parameters, including detailed docs for filter, search, output, sortfield, and raw_json, so the schema already carries parameter meaning. The description adds only the time-window scoping hint and the default sort behavior, both of which are already stated in the schema. 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?

The description opens with a specific verb and resource ('Retrieve the alert log') and immediately defines the resource in domain terms: a read-only record of notifications and remote commands executed by actions. That framing distinguishes it conceptually from sibling tools like action_get or mediatype_get, which return configuration rather than delivery outcomes. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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

Usage Guidelines4/5

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

It gives a concrete use case ('diagnosing why didn't I get notified?') and a direct instruction to use time_from/time_till for time scoping, which tells the agent when this tool is appropriate. It does not name an alternative tool or state when not to use it, so the guidance is contextual rather than exhaustive.

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