Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

httptest_get

Read-only

Retrieve Zabbix web scenarios (HTTP tests) to inspect multi-step HTTP checks, filter by host or status, and return selected properties, counts, or sorted results.

Instructions

Retrieve web scenarios (HTTP tests). Web scenarios perform multi-step HTTP checks against web applications, verifying availability, response time, and expected content. Each scenario contains ordered steps and automatically creates web-monitoring items on the host.

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: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the httptest object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: httptestid, hostid, name, status. Properties: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: agent, delay, http_password, http_proxy, http_user, name, ssl_cert_file, ssl_key_file, ssl_key_password, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only web scenarios that belong to the given hosts.
groupidsNoReturn only web scenarios 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: httptestid, name (a list 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.
httptestidsNoReturn only web scenarios with the given IDs.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
templateidsNoReturn only web scenarios that belong to the given templates.
extra_paramsNoOther native httptest.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), expandName, expandStepName, groupCount, inherited, inheritedTags (8.0+), monitored, tags (6.0+), templated. Switches (true turns one on, false is the same as leaving it out): expandName, expandStepName, 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, selectInheritedTags (8.0+), selectSteps, selectTags (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. Changed11 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",
      +        "evaltype",
      +        "expandName",
      +        "expandStepName",
      +        "groupCount",
      +        "inherited",
      +        "inheritedTags",
      +        "monitored",
      +        "tags",
      +        "templated",
      +        "applicationids",
      +        "selectHosts",
      +        "selectInheritedTags",
      +        "selectSteps",
      +        "selectTags"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native httptest.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), expandName, expandStepName, inherited, inheritedTags (8.0+), monitored, tags (6.0+), templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectHosts, selectInheritedTags (8.0+), selectSteps, selectTags (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."New value: +"Other native httptest.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), expandName, expandStepName, groupCount, inherited, inheritedTags (8.0+), monitored, tags (6.0+), templated. Switches (true turns one on, false is the same as leaving it out): expandName, expandStepName, 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, selectInheritedTags (8.0+), selectSteps, selectTags (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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "agent",
      +        "authentication",
      +        "delay",
      +        "headers",
      +        "hostid",
      +        "http_password",
      +        "http_proxy",
      +        "http_user",
      +        "httptestid",
      +        "name",
      +        "nextcheck",
      +        "retries",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "status",
      +        "templateid",
      +        "uuid",
      +        "variables",
      +        "verify_host",
      +        "verify_peer",
      +        "applicationid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "agent",
      +        "authentication",
      +        "delay",
      +        "headers",
      +        "hostid",
      +        "http_password",
      +        "http_proxy",
      +        "http_user",
      +        "httptestid",
      +        "name",
      +        "nextcheck",
      +        "retries",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "status",
      +        "templateid",
      +        "uuid",
      +        "variables",
      +        "verify_host",
      +        "verify_peer",
      +        "applicationid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the httptest 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: httptestid, hostid, name, status. Properties: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer."New value: +"Properties of the httptest object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: httptestid, hostid, name, status. Properties: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "agent",
      +        "delay",
      +        "http_password",
      +        "http_proxy",
      +        "http_user",
      +        "name",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "uuid",
      +        "applicationid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "httptestid",
      +      "name"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "httptestid",
      +        "name"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: httptestid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: httptestid, name (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": "httptest_getOutput",
      -  "type": "object"
      -}New value: +null
  2. 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=false, so safety is covered. The description adds domain context that scenarios contain ordered steps and auto-create web-monitoring items, which helps interpret results, but says nothing about pagination, default returned fields, or the response wrapper that the raw_json parameter implies.

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 identification front-loaded; the trailing background sentences are informative rather than filler. Slightly more domain lore than an agent strictly needs to invoke 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?

For a 16-parameter tool with no output schema, the description does not describe the returned structure or defaults, leaving the agent to rely entirely on the schema. It is adequate as orientation but thin relative to the tool's parameter richness.

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 16 parameters is already documented in detail, including filter keys, output modes, and search semantics. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 web scenarios (HTTP tests)') and immediately glosses the domain object with multi-step HTTP checks, response time, and content verification. An agent can tell this is the httptest domain retrieval tool, though no sibling is named for contrast.

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 never says when to use this versus the other retrieval tools in the sibling list (host_get, item_get, trigger_get, etc.), nor any prerequisites such as permissions or whether IDs come from another call. Usage is only implied by the tool name.

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