Top error messages
top_messagesIdentify the most common or impactful JavaScript errors by grouping messages, with occurrence and affected-user counts, triage status, first/last seen, and TrackJS links.
Instructions
Error counts grouped by error message, with affected-user counts, triage status, first/last seen and a TrackJS link (GET /errors/messages). Sorted by count descending by default. Best starting point for 'what are our most common / most impactful errors?'. Sort by usercount to rank by number of affected users.
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": "top_messages"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. Defaults to 1. Use paging.nextPage from a previous result to continue. | |
| size | No | Items per page, 1-1000. TrackJS defaults to 20. 20-50 is usually enough for a top-N overview. | |
| sortBy | No | Sort field: count (occurrences, default) or usercount (affected users). | |
| endDate | No | Only include data before this ISO 8601 date/date-time (UTC), e.g. 2026-10-08 or 2026-10-08T00:00:00Z. Precision is 1 second. | |
| startDate | No | Only include data after this ISO 8601 date/date-time (UTC), e.g. 2026-10-01 or 2026-10-01T14:00:00Z. Precision is 1 second. | |
| application | No | Limit results to one TrackJS application key (as configured in TrackJS). Omit for all applications. | |
| sortDirection | No | Sort direction. Defaults to desc. |