Search Deployments
search-deploymentsFind recent deployments for an environment, filtered by status. Choose a deployment to debug its logs.
Instructions
Find recent deployments for an environment, optionally filtered by status. Use this to pick a deploymentLogId for follow-up debug via get-deployment-context.
Use when: user asks for deployment history, wants to find a failed deployment, or needs to pick among multiple recent deployments.
Do NOT use for the latest deployment alone — get-plan-logs or get-error-analysis already cover that without needing an ID.
Returns up to 10 deployments by default (raise limit to 25 max). Sorted newest-first. Each entry includes: id, status, type, queuedAt, startedAt, finishedAt, triggerName, comment, resourceCount, blueprintRevision, blueprintName, blueprintType, prNumber, gitMetadata, planSummary, failedCommand. Set hasMore=true means another page exists.
Prefer filtering via 'statuses' over paging with 'offset'.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| environmentId | Yes | The ID of the environment to list deployments for | |
| statuses | No | Comma-separated deployment statuses to filter by. Common values: SUCCESS, FAILURE, IN_PROGRESS, CANCELLED, ABORTED, WAITING_FOR_USER, TIMEOUT. | |
| limit | No | Maximum number of deployments to return. Defaults to 10, max 25. | |
| offset | No | Number of deployments to skip from the start (newest-first). Use sparingly — prefer filtering via `statuses` first. Helpful only when you need to dig past the most recent page. |