trace_import_artifacts

[external]

Imports existing workspace or artifact-root TRX, MSBuild binlog, log, counters, nettrace, ETL, dump, or GC dump files into a GliderTrace session.

Before you use this tool

Set acknowledgeSensitive=true before importing dump, GC dump, binlog, or ETL artifacts. Raw ETL can contain request values and machine-wide events.

Try it locally in the GliderTrace playground

Parameters

Name	Type	Required	Description
sourcePaths	json	Yes	Artifact file paths under the workspace root or artifact root.
sourceKind	string	No	Optional source kind: 'auto', 'trx', 'binlog', 'log', 'stdout', 'stderr', 'counters', 'nettrace', 'etl', 'dump', or 'gcdump'. Defaults to auto.
captureSourceArtifacts	boolean	No	Copy source files into the new session as sensitive artifact references. Defaults to true. Default: `true`
acknowledgeSensitive	boolean	No	Must be true because this operation may read or store sensitive runtime artifacts. Default: `false`
maxEvents	number	No	Maximum normalized evidence events to import. Clamped to 1..5000. Defaults to 1000. Default: `1000`
label	string	No	Optional short label for the stored session, for example nightly-baseline. Use it to find the session again with trace_list_sessions. Maximum 128 characters.
processId	number	No	Selected worker PID for ETL import. Other PIDs stay outside the normalized evidence.
processStartedAt	string	No	Selected worker start time in UTC. A prior GliderTrace ETW capture can verify it with captureSessionId.
acknowledgeUncertainProcessStart	boolean	No	Accept an unknown start time. The importer leaves events unattributed until ETL lifecycle evidence establishes one incarnation. Default: `false`
captureSessionId	string	No	Original ETW capture session id. The importer checks its stored ETL hash, PID, start time, and capture window before attribution.

Examples

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

Import TRX evidence

Arguments 
{
  "sourcePaths": [
    "TestResults/results.trx"
  ],
  "sourceKind": "trx"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_import_artifacts",
    "arguments": {
      "sourcePaths": [
        "TestResults/results.trx"
      ],
      "sourceKind": "trx"
    }
  }
}

Response Notes

Returns an imported session with artifact references, parsed evidence counts, warnings, and failure summaries. It carries a coverage block. The block reports incomplete when a source was skipped over a size cap or events were dropped.

From GliderTrace 1.1.0: ETL import requires Windows, a selected PID, and start-time evidence or explicit uncertainty. An ETL from an earlier capture can use captureSessionId to verify a copied file. Missing identity, provider, clock, stack, and loss evidence remains explicit.

From GliderTrace 1.0.0: For TRX imports, testCountScope is structured-reports. Complete selected reports can provide exact counts, even when event limits reduce stored findings. Missing or conflicting reports produce partial or unknown counts with a reason and available subtotals. Read count certainty separately from capture coverage.

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.