List monitor events
monitors_events_listList and retrieve events for a specific monitor via a pull API, letting you review event data even when webhooks are not configured.
Instructions
Pull API for a monitor's events — queryable regardless of webhook delivery configuration.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "monitors_events_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| limit | No | ||
| cursor | No | ||
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |