Call page.video_attach
Put a video on a page so the page can play it — 'add my product video to the landing page', 'put the video we just approved on my homepage'. Name the video by its video_id from page.videos: one of the workspace's videos, or a finished video made in Goosy, which is hosted from its approved cut; while that file is still being prepared it answers copying, and the same call made again attaches it. A video with no approved cut yet is refused by name. Attaching a video that is not yet hosted starts hosting it, which charges the workspace for encoding, and captions are charged only when named. On a key with no member behind it the first call returns a confirmation id and the second, carrying it back, attaches. Not for taking a video off — that is page.api_video_detach.
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.video_attach
- 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.