Call page.run_build
Build the site again and say what the build reports — 'try building it again', 'build it now', 'did that fix the build?', 'run it again and see if it works'. No site id is needed — it works on the site the member has open on screen. It builds the site's current checkpoint on the rail again — after a build failed for a reason you have fixed, or to re-run one. Every change to the site's files already builds, so you rarely need this. The tool waits a short while: a build that finishes in time answers with its outcome, and a FAILED build answers with the failing step's log tail — read it and fix the file it names. A build still running answers still_running: true with its run id; the member's editor shows the log as it lands, and page.checkpoint reports the outcome later. Not for reading why the last build failed without re-running it — that is page.checkpoint.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/page.run_build
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 6 revisions of this API.