Get site details
get_siteReturn one site's details: live URL, status, plan, served file paths, whether editable source is stored (and its build settings), custom domains, bandwidth and the last 10 deploys. Use get_site to inspect a site before editing it; use list_sites to find site names, and get_app_status for container services.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_site"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Site name as shown by list_sites, e.g. my-portfolio. Provide name or siteId. | |
| siteId | No | Site id from list_sites or get_site. Use instead of name. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| name | Yes | ||
| plan | Yes | ||
| files | Yes | Number of files the site serves now (live count). After a patch deploy it can exceed the last deploy's fileCount. | |
| siteId | Yes | ||
| status | Yes | Lifecycle state. Sites are usable only in 'active'. 'deleted' is the soft-delete recovery bucket (returned until the team's restore window expires and the sweeper purges the row). 'deleting' is the transient state of an in-flight hard-delete request. | |
| history | Yes | ||
| bandwidth | Yes | ||
| filePaths | No | Site-relative paths of every served file, to pick paths to read, patch or delete. Omitted when the pod cannot be inspected (e.g. not ready); `files` then falls back to the last deploy's fileCount. | |
| lastDeployAt | Yes | ||
| sourceStored | Yes | Whether editable source is stored. Read and edit source, then build_and_deploy when true. | |
| customDomains | Yes | Custom domains of this site and the team's custom-domain allowance; null when they could not be read. | |
| sourceManifest | Yes | Saved source build settings. Preserve these when rebuilding. |