page

Call page.videos

List the videos a page plays and the workspace videos it could play, each with whether it is ready, and the finished videos made in Goosy that could go on it — 'which videos are on the landing page?', 'is my upload ready to play yet?'. Attached ones carry the player address a page embeds; a template's video shows as source template; an approved video made in Goosy that is not hosted yet is listed under finished by its title, with the video_id page.api_video_attach takes. It reads only. Not for putting a video on the page — that is page.api_video_attach.

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.videos

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/page.videos
  • 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
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 7 revisions of this API.