get_v1_platform_sites_slug_releases
ListReleases returns a site's releases newest-first, marking the active one — the rollback menu.
ListReleases returns a site's releases newest-first, marking the active one — the rollback menu.
Each row carries the release id to activate, the source it was promoted from, its object and byte counts, and the URL if it is the one serving. Retention bounds the list, so it is the set that can actually still be rolled back to, not a full history.
Scope: a validated principal is required (403 without one) and the site is resolved within that principal's org, so another tenant's slug is a 404.
| Tool | get_v1_platform_sites_slug_releases |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1, 1 required |
| Operation | GET /v1/platform/sites/{slug}/releases |
| Product | platform |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
slug | string | yes | — | — | Slug is the project to act on, from the path. It is unique within the caller's org and nowhere else, so another tenant's slug is a 404. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/platform/sites/{slug}/releases, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_platform_sites_slug_releases",
"arguments": {
"slug": "<slug>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_platform_sites_slug_releases | GET /v1/platform/sites/{slug}/releases | platform | Returns a site's releases newest-first, marking the active one — the rollback menu. |
The same capability over plain HTTP is in the platform API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?