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

**Snapshots.** A row's snapshots — scheduled, manual, safety and copy snapshots with their status, size, note and whether each is protected — its snapshot settings, and the restore running on it, if any. Scope: read.

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

## When to use it

A row's snapshots — scheduled, manual, safety and copy snapshots with their status, size, note and whether each is protected — its snapshot settings, and the restore running on it, if any.

A scheduled snapshot that failed is tried again automatically: until its last attempt it reads `retrying`, never `failed`, and the earlier attempts are not listed.

A snapshot deleted in the last day is still listed, with `delete_reason` and `delete_reason_label`. The reason can be `retention`, `quota`, `manual`, `failed_cleanup`, `cluster_deleted`, `clone_cleanup`, `operator_expired`, `site_purged`, `rehome_expired` or `volume_retired` (corestack_snapshot_get says what each means).

While restoring anywhere is switched on, each snapshot also says whether it is `kept`, `in_use` (a restore or a copy is reading it) and `available` (restorable now), with `unavailable_reason` when it is not.

For a CoreStack site, `settings.per_site` is `true` and the snapshot space is the site's own package's, measured over the site and its environments, the same figures as the Snapshots tab's Snapshot space meter: `quota_bytes`, `usage_bytes` (`null` until the platform has measured sizes for the first time, at `usage_synced_at`), `protected_bytes` (snapshots marked to keep) and `protect_cap_bytes` (how much may be kept). `over_quota` says the usage is above the quota, and `pruned_recently` that snapshots were deleted early in the last 24 hours to stay within it. A site on your own CoreCluster has `per_site: false` with these figures `null`, `0` or `false`: corecluster_snapshot_settings_get answers that CoreCluster's quota.

These figures measure the whole site, its environments included. A grant pinned to one environment, not to its site, gets `usage_bytes`, `usage_synced_at`, `protected_bytes`, `pruned_recently` and `over_quota` as `null`; the package's `quota_bytes` and `protect_cap_bytes` are still given.

## Inputs

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

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_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_list",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_snapshot_list with site_id 4211. (Snapshots.) Tell me what it returned.
```

## The same task elsewhere

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