# get_restore_status

> Check how a backup restore is going, or why it did not finish.

- Tier: R
- Required scope: read:hosting
- Annotations: readOnlyHint, idempotentHint
- Docs: https://api.inleed.com/tools/get-restore-status

## Description

Check how a backup restore is going, or why it did not finish. A restore is asynchronous: `restore_backup` queues it and this is the other half. With `restore_id` it returns `status` (pending, processing, completed, partially_completed, failed, aborted, never_finished), `phase` (which step it is on), `percentage`, `itemsCompleted` of `itemCount`, `problems[]` with JetBackup's own message for each part that did not restore, and a plain-language `summary` with the next step — relay that summary, it already says whether the account is now part-restored. Without `restore_id` it lists this account's recent restores, which is how you find one started in the control panel or by support.

## Input schema

- `input` — string (required). A domain, email address, website URL, numeric service id, or hosting-account username the customer actually owns. Resolved to the owning account automatically; the resolved target is echoed back in the response.
- `restore_id` — string. The restore to follow, from restore_backup → restoreId or from this tool's own restores[].id. Omit to list the account's recent restores.
- `limit` — integer. How many recent restores to list, newest first (1–50, default 10). Ignored when restore_id is given.

## Example call

```json
{
  "name": "get_restore_status",
  "arguments": {
    "input": "example.se"
  }
}
```