// Confirm artifacts are up to date after dbt run or a known artifact change. Use before re-running analysis on the same target.
| name | refresh-snapshot |
| description | Confirm artifacts are up to date after dbt run or a known artifact change. Use before re-running analysis on the same target. |
| compatibility | dbt-tools on PATH; bind-target and check-session already applied. |
Handle: dbt-tools-cli:refresh-snapshot
status reflects current files (ages / readiness)bind-targetdbt or artifacts were updated externallybind-target)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.