units

Call units.add_to_board

Put this video unit on a board, linked as a reference — 'add this video to that board', 'put this on the board as a reference'. Add THIS video unit to a board, linked as a reference. The unit stays where it is — nothing is copied or moved, and the board does not become its owner. When the member asked for it themselves it runs; otherwise they see an approve card first. Not for landing the video on a course or project as its home: that is the Approve step's own 'Where it saves' question, answered on the Approve page, not a verb. Never say it is done unless the result says it is.

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/units.add_to_board

Request

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

unit_idstring uuid required

The video unit to add, as a UUID. Take it from the conversation's context — never invent one.

board_idstring uuid required

The board to add it to, as a UUID. Ask the operator which board if they have not named one; never guess.

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 6 revisions of this API.