// Filter and sort run_results node executions by status, time, and warehouse metrics. Use for post-run triage and slow-node investigation.
| name | query-executions |
| description | Filter and sort run_results node executions by status, time, and warehouse metrics. Use for post-run triage and slow-node investigation. |
| compatibility | dbt-tools on PATH; run_results required (check-session readiness full). |
Handle: dbt-tools-cli:query-executions
unique_id pattern; warehouse-specific options when relevantbind-targetcheck-session — readiness: full (requires run_results.json)summarize-run)Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check MCP session state—target, load time, stale flag, runs, warehouse type. Use as a gate before analysis primitives.
Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check whether dbt artifacts exist, are fresh, and which readiness level applies. Use as a gate before manifest- or run_results-based analysis.
Return metadata and context for one dbt resource by unique_id. Use when explaining what a model, source, or test does.
Find dbt resources by name, type, tag, package, or path. Use to resolve unique_id before describe-resource, trace-dependencies, or query-executions.