page

Call page.set_access

Propose, then confirm, making one page of a site members-only — so only signed-in members of the workspace can open it — or public again: 'make the team page private', 'open /pricing to everyone again'. A live site rebuilds and publishes itself with the change; a draft site's change lands with its next build. It sets one page by its path, never a pattern such as '/admin/*' — relay that refusal, which says a pattern is edited in the site's source. Not for publishing a built version — that is page.api_publish.

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.

post/api/v1/tools/page.set_access

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/page.set_access
  • Auth: HTTP bearer

Headers

x-request-idstring

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

site_idstring uuid required
pathstring required
access'members' | 'public' required
confirmation_idstring uuid
workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

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.

OR

Changes

No recorded changes to this operation across all 4 revisions of this API.