videos

Call videos.stock_pull

'find a real shot for this scene', 'use a real clip of a desk here' — find a real-world shot for one storyboard scene and drop it in as an insert of a few seconds; it never replaces the scene, and the answer names who took it with a link. It answers in two calls: without confirmation_id it says what would be looked for and for how long, and searches nothing; the same call again with that confirmation_id, on a member's own API key, searches, keeps the shot in this workspace's clips and places it. Not for a made clip when nothing real will do — that is videos.generate_clip.

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

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/videos.stock_pull
  • 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

video_idstring uuid required

The video's id, as given in this conversation.

scene_idstring required

The scene's id, as given in the storyboard.

looking_forstring required

What the shot should be of, in a few words.

secondsinteger

How long the shot runs inside the scene — a few seconds.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

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.