project_deploys
List the recent deploy history for a project — successful deploys AND rejected/failed deploy attempts, interleaved by time (up to 150 successful releases plus 20 failed attempts). Each entry has a status field so you can tell a success from a rejection at a glance.
Example:
{ "project_id": "my-saas" }
// Returns: { "deploys": [
{ "status": "success", "version": 12, "promoted_at": "2026-04-20T...", "is_live": true, "commit_sha": "...", "deployed_by": { "user_id": "...", "email": "..." } },
{ "status": "rejected", "version": 11, "reason": "BUNDLED_DEPLOY_REJECTED", "message": "This looks like pre-built output...", "at": "2026-04-19T...", "is_live": false },
{ "status": "success", "version": 10, "promoted_at": "2026-04-18T...", "is_live": false }
] }A rejected entry's version is the version it WOULD have become (may be null); it never went live. Each successful entry carries rollback_available, describing retained build availability. A false entry cannot be restored; true still requires schema-safe activation. project_rollback selects the previous activation; project_restore_version selects a retained version by number. Free covers the last 24 hours. Paid plans cover any retained version. Failure entries also include failure_id, a safe classification, and remediation. somewhere api GET /v1/deploy/failure/<failure_id> resolves one exact reference; the endpoint requires access to the owning project and never returns the private stack or provider diagnostic.
Each successful version shows its user-supplied note, if any, and the restore call when available. You can add a note when publishing or later. Each successful entry also carries build: { recorded: true, reported_cli_version, platform_version_id, platform_version_tag, runtime_build_version } — the CLI version the deploying client reported (its own claim, null when none was sent, e.g. an MCP deploy), the API build that published the release (the separate compiler build is not recorded), and the runtime build baked into its functions (null without functions). A release built without identity recording (including by older code during rollback) returns { recorded: false, reason: 'built_without_identity_recording' }; it is never guessed.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>"
},
"name": "project_deploys"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID, subdomain, or 'default'. |