trace_list_sessions

[analysis]

Lists stored GliderTrace sessions from the local session index, with filters for mode, status, label, and start time.

Try it locally in the GliderTrace playground

Parameters

Name	Type	Required	Description
mode	string	No	Optional session mode filter: 'run', 'test', 'build', 'restore', 'attach', 'dump', 'gcdump', or 'import'.
status	string	No	Optional session status filter: 'created', 'running', 'completed', 'failed', 'timeout', or 'cancelled'.
label	string	No	Optional label filter. The value must be the whole stored label. Letter case is ignored.
since	string	No	Optional ISO 8601 date and time. Only sessions that started at or after this time are returned.
limit	number	No	Maximum number of sessions to return. Clamped to 1..200. Defaults to 50. Default: `50`
cursor	string	No	Pagination cursor returned by a previous call.

Examples

Replace sample paths and symbol keys with values from your workspace.

Find a labelled baseline run

Arguments 
{
  "label": "nightly-baseline"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_list_sessions",
    "arguments": {
      "label": "nightly-baseline"
    }
  }
}

Response Notes

Returns session id, mode, status, exit code, start and end times, byte size, pinned state, and label, with a pagination cursor.

GliderTrace 1.0.0 returns compact JSON for every tool. Result fields appear beside success; there is no response-format parameter. success describes the tool call. Check the process or session status and exitCode separately. Scalar results and fields that conflict with reserved names appear under result.

To migrate an envelope consumer, read response.sessionId instead of response.data.sessionId. Stored sessions and exported files keep their formats. --max-response-chars limits response text to 60,000 UTF-16 characters by default. Use 0 to disable it, or at least 1,000. This limit counts text characters, not transport bytes or tokens.

outputLimit.truncated marks omitted response detail. It does not change capture completeness. Use the returned next tool and arguments when available. Do not repeat a command or feedback submission to recover omitted output. For event pages, keep the filters and cursor while reducing limit.

For session details, set includeArtifacts and includeTopFindings to false to reduce output. Check error, actionable meta, warnings, and coverage before drawing conclusions. Internal diagnostics stay in local server logs.