trace_export

[analysis]

Exports a compact GliderTrace agent summary or zip artifact reference for a session.

Before you use this tool

Zip exports can include raw artifacts when includeRawArtifacts=true.

Try it locally in the GliderTrace playground

Parameters

Name	Type	Required	Description
sessionId	string	Yes	Trace session id, for example trc_20260507_123044_ab12cd34.
format	string	No	Export format: 'agent-summary-json', 'agent-summary-md', 'ci-summary-json', 'ci-summary-md', 'sarif', or 'zip'. The sarif format writes a SARIF 2.1.0 file of build and test findings for code scanning. On a pipeline session it writes one run per stage. Default: `"agent-summary-json"`
includeRawArtifacts	boolean	No	Include sensitive raw artifacts in zip exports. Defaults to false. Default: `false`

Examples

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

Export an agent summary

Arguments 
{
  "sessionId": "trc_20260507_123044_ab12cd34",
  "format": "agent-summary-md"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_export",
    "arguments": {
      "sessionId": "trc_20260507_123044_ab12cd34",
      "format": "agent-summary-md"
    }
  }
}

Export SARIF findings for code scanning

Arguments 
{
  "sessionId": "trc_20260507_123044_ab12cd34",
  "format": "sarif"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_export",
    "arguments": {
      "sessionId": "trc_20260507_123044_ab12cd34",
      "format": "sarif"
    }
  }
}

Response Notes

Returns summary content or a local artifact bundle reference, depending on export format. It carries a coverage block. The exported summary payload echoes the block when evidence was dropped or bounded at capture.

From GliderTrace 1.0.0: Test summaries preserve unknown counts, count provenance, and available report subtotals. Source candidates remain unverified in exported evidence.

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.