get_pipeline_status
Read pipeline ingestion status after run_tap to monitor submitted jobs, poll until all are done, and check the final success, warning, or error outcome.
Instructions
Read pipeline ingestion status. Use this after run_tap to watch a tap-submitted load progress. Pass publisher_token to see every job the tap run submitted (the recommended option — works for both structured and document taps). Pass pipeline_token for a single ingestion job. Exactly one of the two must be supplied. Response shape: {rollup: {allDone, status, jobs: [...]}, events: [...]}. Poll every few seconds until rollup.allDone is true, then read rollup.status (success | warning | error) for the outcome. Per-job detail is in rollup.jobs[] — each entry has pipelineToken, pipeline, filename, status, startedAt, lastEventAt, elapsed, and lastError (populated on failure with processName and description). events[] is the raw begin/info/end audit trail if you need it; the rollup is the source of truth for completion. A failed run's description gives the error and its causes in plain words; the full stack trace is not included here (it is in the server log under the run's token and in the Ops activity view).
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": "get_pipeline_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pipeline_token | No | UUID for a single ingestion job. Returns status rows for that one job. | |
| publisher_token | No | UUID returned from run_tap response. Returns status rows for ALL jobs this tap run submitted. |