Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

action_get

Read-only

Retrieve Zabbix actions that define automated event responses, filter by event source, and include operation details to inspect event-driven workflows.

Instructions

Retrieve actions that define automated responses to Zabbix events. Actions tie conditions (e.g. trigger severity, host group membership) to operations (e.g. send message, execute script, close problem). Filter by event source to narrow results: 0=trigger, 1=discovery, 2=autoregistration, 3=internal, 4=service. Use selectOperations, selectRecoveryOperations, selectUpdateOperations in the output to include the full operation definitions.

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: actionid, esc_period, eventsource, name, notify_if_canceled (6.0+), pause_suppressed, pause_symptoms (6.4+), status. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the action object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: actionid, name, status, eventsource. Properties: actionid, esc_period, eventsource, name, notify_if_canceled (6.0+), pause_suppressed, pause_symptoms (6.4+), status.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: esc_period, name.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only actions that reference these host IDs in their conditions.
groupidsNoReturn only actions that reference these host group IDs in their conditions.
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 actions with the given IDs.
sortfieldNoSort by one or more of: actionid, name, status (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
triggeridsNoReturn only actions that reference these trigger IDs in their conditions.
countOutputNoReturn the count of matching results instead of the actual data.
eventsourceNoReturn only actions with the given event source. Values: 0 = trigger events, 1 = discovery events, 2 = autoregistration events, 3 = internal events, 4 = service events.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
extra_paramsNoOther native action.get parameters, merged into the request as-is. Parameters: mediatypeids, scriptids, userids, usrgrpids. Sub-object selects (value 'extend', 'count' or a list of property names): selectFilter, selectOperations, selectRecoveryOperations, selectUpdateOperations (6.0+). 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. Changed10 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": [
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "mediatypeids",
      +        "scriptids",
      +        "userids",
      +        "usrgrpids",
      +        "selectFilter",
      +        "selectOperations",
      +        "selectRecoveryOperations",
      +        "selectUpdateOperations",
      +        "selectAcknowledgeOperations"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "actionid",
      +        "esc_period",
      +        "eventsource",
      +        "name",
      +        "notify_if_canceled",
      +        "pause_suppressed",
      +        "pause_symptoms",
      +        "status"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "actionid",
      +        "esc_period",
      +        "eventsource",
      +        "name",
      +        "notify_if_canceled",
      +        "pause_suppressed",
      +        "pause_symptoms",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the action 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: actionid, name, status, eventsource. Properties: actionid, esc_period, eventsource, name, notify_if_canceled (6.0+), pause_suppressed, pause_symptoms (6.4+), status."New value: +"Properties of the action object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: actionid, name, status, eventsource. Properties: actionid, esc_period, eventsource, name, notify_if_canceled (6.0+), pause_suppressed, pause_symptoms (6.4+), status."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "esc_period",
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "actionid",
      +      "name",
      +      "status"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "actionid",
      +        "name",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: actionid, name, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: actionid, name, status (a list for several; pair with 'sortorder'). No other property is sortable."
    • 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"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "action_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and a closed world, so the safety profile is covered. The description adds one genuinely behavioral detail: that operations must be requested via selectOperations/selectRecoveryOperations/selectUpdateOperations rather than returned by default. It says nothing about permissions, pagination defaults, or result volume, and does not touch the raw_json prompt-injection tradeoff documented in the schema.

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 sentences, front-loaded with the core concept, then filtering, then output expansion. Nothing is wasted structurally, though the eventsource enumeration is redundant with the schema and pushes length up without new information.

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?

For a 17-parameter read tool with no output schema, the description covers what an action is, the most important filter, and how to expand nested operations, which is the essential minimum. It leaves the agent to discover pagination (limit), delegate-style host/group/trigger filtering, and count/raw_json behavior entirely from the schema, which is acceptable but not thorough.

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 baseline is 3. The description's eventsource value mapping (0=trigger through 4=service) and the selectOperations guidance duplicate what the eventsource and extra_params schema entries already state, so it adds little meaning beyond structured fields.

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 actions') and explains the domain concept: actions tie conditions to operations. An agent can tell this is about Zabbix automation actions rather than alerts, correlations, or scripts. It never explicitly names a sibling tool it differs from (e.g. correlation_get or alert_get), which keeps it from a 5.

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?

Offers implied usage guidance: 'Filter by event source to narrow results' and 'Use selectOperations... to include the full operation definitions', which tells the agent how to get complete output. However, there is no explicit when-to-use / when-not-to-use statement or named alternative for related read tools such as correlation_get or script_get.

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