get_lineage
Traverse the lineage graph upstream and downstream of a tap, pipeline, dataset, or catalog to run impact analysis before changes and confirm which datasets a pipeline actually wrote.
Instructions
Traverse the lineage graph from one node: everything upstream (what feeds it) and/or downstream (what depends on it) of a source, tap, pipeline, dataset, or catalog, with the edges between them, freshness for the pipeline involved, and optionally the most recent recorded runs (what each run read and wrote, per destination). Datasets a pipeline used to land into under an earlier configuration are marked historical. Use it for impact analysis before changing or deleting something — 'what is downstream of this tap?' — or to see which datasets a pipeline actually wrote. Node names: a tap or pipeline name; a dataset's kind:coordinates id as returned by find_data or list_pipelines lineage; a source host; a catalog name.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"node_type": "<node_type>",
"name": "<name>"
},
"name": "get_lineage"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The node's name (the part after `type:` in a lineage id). | |
| runs | No | Include this many most-recent recorded runs for the node (default: 0, max: 50). | |
| depth | No | Maximum hops from the node (default: unbounded). | |
| columns | No | For pipeline and dataset nodes, include column-level lineage: which destination columns pass through from which source fields (exact), which the platform adds (system), and any cached AI-inferred mappings for the transformation. Default: false. | |
| direction | No | Which way to traverse (default: both). | |
| node_type | Yes | The kind of node to start from. |