Session
glitchless_sessionOne play session, or without session_id the latest sessions (who played, when, for how long, how far they got, the session type), to find one: the developer's own playtest to mark with glitchless_mark_known (player), a crash to open. With session_id, by default a summary an agent can hold: the device, then each level in the order it was played (when it was first reached, the time spent on it, tries, completions, deaths and their causes, the game's own events counted, hitches with the worst and their causes, frame rate, errors, rage inputs with where the player stood, and how it ended there), time outside levels (menus, a title screen), the worst hitches, errors, bug reports, and the outcome (crashed, rage quit, the last level). With level or types, the events themselves (levels with their attributes, deaths with positions, errors, hitches with causes, custom events, counters once a window, disconnects, agent annotations), each with at_s, seconds from the start: types "death,hitch" or a custom event name "room_done"; "frames" adds the per-5s frame windows. view "timeline" gives every event (long: a 10-minute session has hundreds). Use with session ids from errors, hitches, rage quits, rage inputs or a match. A game server's session (service ".server") gives its tick windows.
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": "glitchless_session"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | Only include sessions from this environment, e.g. "prod" (what the game passes to init; builds a developer runs usually send "dev") | |
| game | No | The game, by name or id, when signed in to a workspace (glitchless_list_games lists them); later calls keep it. With a key for one game (gl_sk_…), a call that names another game is refused: sign in to the workspace to reach every game. | |
| view | No | "summary" (default, unless level or types is given): level by level; "timeline": the events themselves | |
| hours | No | Look-back window in hours (default 24), as far back as the workspace keeps data on Glitchless Cloud (the answer says when it starts later than asked). Past 744 (31 days) answers are by day. | |
| level | No | Only this level's events: its own and what happened while it was played | |
| limit | No | With the timeline: at most this many events (default 150), from the first | |
| types | No | Only these, comma-separated: event types (death, hitch, error, custom, level_start, bug_report…), custom event names (room_done), or "frames" for the frame windows | |
| service | No | Game service name (defaults to the most recently active game) | |
| version | No | Only include sessions from this game version | |
| session_id | No | Session id (s_…); without it, the latest sessions | |
| session_type | No | "user": players only; "tester": people on TestFlight and other test builds only; "synthetic": bots, playtests and store test devices only; "all" or unset: every session. Findings (glitchless_triage, and the overview's) read the production sessions of players unless env or session_type is given |