# release_status > Where a release is: draft, in review, approved, live or rejected (with the reason), and its delivery state store by store with store links. Tool `release_status` · Read-only · Every account with MCP access · Role permission: `releases.view` Where a release is: draft, in review, approved, live or rejected (with the reason), and its delivery state store by store with store links. Identify it by release_id (from search_catalog), UPC, a track ISRC or title. If several match, returns the matches to pick from. ## Arguments | Argument | Type | Required | Description | | --- | --- | --- | --- | | `release_id` | integer | No | | | `upc` | string | No | | | `isrc` | string | No | | | `title` | string | No | Release title (partial match). | ## Example call Assistants make this call for you; this is what goes to `https://app.hillsmusic.com/mcp` over JSON-RPC. ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "release_status", "arguments": {} } } ``` ## Result A one-line summary as text, then the same data as JSON in `structuredContent`, with these fields: | Field | Type | Description | | --- | --- | --- | | `release` | object or null | | | `matches` | array of object | | | `tracks` | array of object | | | `stores` | array of object | | | `store_summary` | object | | A refusal (no permission, not found, bad input) comes back as a tool error (`isError: true`) whose text says why. Source: https://developer.hillsmusic.com/mcp/release-status/