getFailureLogs
Fetch session logs for a test by session ID to debug failures; use failuresOnly to return only error, exception, and stack-trace lines.
Instructions
Fetch and return session log file content (selenium, browser, chrome, vm, appium) for a test by session ID. Use this to debug failures — pass failuresOnly=true to extract only error/exception/stack-trace lines.
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": {
"sessionId": "<sessionId>"
},
"name": "getFailureLogs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| logTypes | No | Which log types to fetch. Defaults to every type available on the test. Valid: selenium, browser, chrome, vm, appium. | |
| sessionId | Yes | The session ID of the test | |
| timeoutMs | No | Per-log fetch timeout in milliseconds (default 15000). | |
| failuresOnly | No | If true, only return lines that match error/exception/stack-trace patterns (plus 1 line of context above/below). | |
| maxBytesPerLog | No | Truncate each log to the last N bytes (default 50000, max 1000000). Failure context typically lives near the end. |