Skip to main content
Glama
CoveoSec
by CoveoSec

v2_alerts_get_alerts_multi_events

Retrieve alerts with multiple events from Cortex XSIAM, applying filters with AND logic and pagination to get up to 100 results.

Instructions

Get Alerts Multi-Events v2

Get a list of alerts with multiple events.

  • The response is concatenated using AND condition (OR is not supported).

  • The maximum result set size is 100.

  • Offset is the zero-based number of alerts from the start of the result set.

Cortex XDR displays in the API response whether a PAN NGFW type alert contains a PCAP triggering packet. Use the Retrieve PCAP Packet API to retrieve a list of alert IDs and their associated PCAP data.

Note: You can send a request to retrieve either all or filtered results.

Required license: Cortex XSIAM Premium or Cortex XSIAM Enterprise or Cortex XSIAM Enterprise Plus

[POST /public_api/v2/alerts/get_alerts_multi_events] · Incidents

Example request body:

{
  "request_data": {
    "filters": [
      {
        "field": "severity",
        "operator": "in",
        "value": [
          "medium",
          "high"
        ]
      }
    ]
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_dataYesA dictionary containing the API request fields. An empty dictionary returns all results.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination limits, offset semantics, AND-only filter behavior, optional all/filtered retrieval, license requirements, and PCAP-related response details. However, it does not describe the full return object structure or explicitly state that this is a read-only operation, leaving some behavioral ambiguity.

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?

The description is front-loaded with the purpose and uses bullets for constraints, followed by license, endpoint, and an example body. It is somewhat long but each section adds useful information; minor redundancy exists in repeating the tool name, but overall it is well-organized.

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 read/list tool with no output schema, the description covers purpose, filtering behavior, pagination, example request, and license requirements. It is operationally usable, though it lacks explicit sibling-tool guidance and a thorough description of the response payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% parameter coverage, so the baseline is 3. The description adds value by providing a concrete example request body and clarifying that multiple filters are combined using AND, with OR unsupported, which enriches the meaning of the filters parameter beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Get a list of alerts with multiple events,' which states a specific verb and resource. The title and endpoint ('v2') further distinguish this from sibling tools like v1_alerts_get_alerts_multi_events and alerts_get_alerts.

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?

The description provides clear usage context: AND-only filter combination, maximum result size of 100, zero-based offset, ability to retrieve all or filtered results, and required licenses. It does not explicitly name alternatives or state when not to use this tool, but the constraints are operationally actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CoveoSec/xsiam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server