browserless_logs
Read Browserless's recent request logs to diagnose runs that failed on the Browserless side, with outcomes, failure reasons, durations, and costs.
Instructions
Read Browserless's own record of the account's recent requests: what was attempted, whether it failed, why it stopped, how long it took and what it cost. This is the tool for diagnosing a run that failed on the Browserless side rather than in your own code. The window available depends on the account plan; the server reports the limit if a range is refused. Read-only. When an inline view can be prepared, MCP Apps clients receive a viewRef; use browserless_show to display the request-log explorer. Its rows and pagination cursors stay in widget-only metadata. Otherwise returns the standard Markdown result.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "browserless_logs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Filter by the target URL of the request. | |
| limit | No | Maximum entries to return, 1-100. Defaults to 50. | |
| order | No | Timestamp order. Defaults to newest first. | |
| cursor | No | Opaque cursor returned as `nextCursor` by the previous page. | |
| levels | No | Severity levels to include. Omit for all levels. | |
| reason | No | Filter by the specific failure reason within a category. | |
| endTime | No | Exclusive RFC 3339 end time. Defaults to now when omitted. | |
| outcome | No | Filter by request outcome, e.g. `failed` or `succeeded`. | |
| apiKeyId | No | Restrict to one API key, by id. Get ids from browserless_account with action "keys". | |
| category | No | Filter by failure category, e.g. `browserless_refused`, `browserless_killed`, `target_error`. | |
| endpoint | No | Filter by endpoint, e.g. `/chromium/bql` or `/screenshot`. | |
| requestId | No | Return only entries for one request id. | |
| startTime | No | Inclusive RFC 3339 start time. Omit to let the account’s plan decide how far back to look — the available window is plan-dependent and the server rejects a range that exceeds it. | |
| eventNames | No | Filter by lifecycle event name, e.g. `request.failed`, `bql.*.failed`. |