generation_defaults

Call generation_defaults.set

Set what new work starts from by default — 'make vertical the default for videos', 'new emails should start as newsletters', 'change the default thumbnail style'. Set ONE of the workspace's generation defaults — the video format, render mode, thumbnail profile or email type new work starts from. Admin only; the action refuses anyone below that role. It changes what LATER generations start from and starts none itself. Not for a lasting preference in the operator's own words — that is taste_note.add.

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/generation_defaults.set

Request

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

field'videoFormat' | 'renderMode' | 'thumbnailProfile' | 'emailType' required

Which generation default to set.

valuestring nullable required

The value to set, taken VERBATIM from an option the defaults page listed for this knob — never invented, never a plausible-looking guess. The write path does NOT check the value against a catalogue: whatever is passed is trimmed and stored as the workspace's default, so a wrong value is saved rather than refused. Ask the operator which listed option they mean when you are not certain. Pass null to clear the knob and fall back to the built-in.

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.