corestack_ deployments_ pipeline_ versions_ list
Pipeline versions.
When to use it
List a binding's saved pipeline versions, newest first: who saved each, when, from where (source), which stages or settings it changed, and whether it can be restored (the kept version from before the conversion and the current one cannot). Pass stage for only the versions that changed that stage or the settings. Read one with corestack_deployments_pipeline_get version_id, restore one with corestack_. Every kept version is on one page.
The same action in the public REST API, with the same checks, refusals and scope: GET / (stage).
Ask for it
Using the Corefinity MCP server, call corestack_deployments_pipeline_versions_list with site_id 4211, stage post_deploy. (Pipeline versions.) Tell me what it returned.Inputs
Default: the environment's default binding. At least 1.
Every kept version is on one page: next_cursor is always null. Up to 200 characters.
At least 1.
Only the versions that changed this stage or the settings.
builddatabasepost_deployExample call
{
"name": "corestack_deployments_pipeline_versions_list",
"arguments": {
"site_id": 4211,
"stage": "post_deploy"
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |