---
title: "corestack_snapshot_get"
url: https://docs.corefinity.com/mcp/tools/corestack_snapshot_get
type: tool
last_updated: 2026-11-13
feature: snapshots
related:
  - https://docs.corefinity.com/api/reference/backups/get-snapshot.md
  - https://docs.corefinity.com/guides/sites/backups/snapshots.md
---
# corestack_snapshot_get

**Snapshot.** One snapshot: its status (pending, creating, ready, failed, deleting, deleted; a scheduled snapshot that failed and will be tried again reads retrying, and an attempt a later one replaced reads retried), kind, size, note, whether it is protected and whether it can be restored. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

One snapshot: its status (pending, creating, ready, failed, deleting, deleted; a scheduled snapshot that failed and will be tried again reads retrying, and an attempt a later one replaced reads retried), kind, size, note, whether it is protected and whether it can be restored.

Once it is being deleted, `delete_reason` says why and `delete_reason_label` says it in words. It can be `retention` or `quota` (its snapshot policy: a CoreCluster's snapshot settings for a site on a CoreCluster, its package's retention and quota for a CoreStack site), `manual` (someone deleted it), `failed_cleanup`, `cluster_deleted`, `clone_cleanup` (taken to copy an environment, removed once the copy was done), `operator_expired` (taken by Corefinity for a move, removed once it was settled), `site_purged` (its site was removed for good), `rehome_expired` (a deleted environment's final snapshot, kept for its days) or `volume_retired` (earlier storage was retired). A deleted snapshot keeps the reason it was recorded with, so one deleted before those reasons were recorded can say `retention` for any of those clean-ups (for example, the snapshot a copy was taken from, removed once the copy was done).

## Inputs

- `snapshot_id` (integer, ≥ 1, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "snapshot_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "snapshot_id"
  ],
  "type": "object"
}
```

## Refusals

- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_snapshot_get",
  "arguments": {
    "snapshot_id": 9051
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_snapshot_get with snapshot_id 9051. (Snapshot.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/snapshots/{snapshot}](https://docs.corefinity.com/api/reference/backups/get-snapshot.md)
- Guide: [Backups](https://docs.corefinity.com/guides/sites/backups/snapshots.md)
