---
title: "Call videos.write_script"
method: POST
path: "/api/v1/tools/videos.write_script"
tags: ["videos"]
---

# Call videos.write_script

`POST /api/v1/tools/videos.write_script`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/videos.write_script`
- Auth: HTTP bearer

'write the script for this video', 'rewrite the script to be more casual' — write one video's script from its plan, or rewrite it under one direction you pass. The answer carries the chapters and any facts the script still needs. This runs a PAID writing turn: on a member's own key it writes in one call; on a key with no member behind it the first call describes what would be written, charges nothing and returns a confirmation id, and the second, carrying that id back, is what writes it. Not for drawing the scenes — that is `videos.draw_storyboard`.

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.

## Headers

- `x-request-id` string
- `Idempotency-Key` string

## Request body

- object
  - `video_id` string, uuid, required: The video's id, as given in this conversation.
  - `direction` string: The direction for a fresh draft from the plan, in the person's own words. Leave it out for the first pass.
  - `confirmation_id` string, uuid: Only when a first call answered confirmation_required: send that id back, unchanged, to run the recorded request. On your own member key the first call already runs, and there is no id.
  - `idempotency_key` string: Deprecated on REST: send the `Idempotency-Key` header instead. Still accepted until 2026-12-31; if both are sent they must match.
  - `workspace` string: 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 `200`

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.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `video_id` string
    - `chapters` object[]
      - `number` integer, required
      - `name` string, required
      - `text` string, required
      - `seconds` integer, required
      - `made_by` 'you' | 'goosy', required
    - `words` integer: How long the script runs, in words.
    - `length_words` string
    - `step` 'idea' | 'writing' | 'storyboarded' | 'needs_filming' | 'edited' | 'ready' | 'scheduled' | 'live'
    - `open_at` string: Where the person reads it.
    - `questions` object[]: Facts Goosy needs and does not have. Ask the person these AS YOUR NEXT TURN, in your own words, in one message. Never answer one yourself and never guess: a made-up name, number or place ships in the finished video, and the video will not go down while a blank stands.
      - `key` string, required
      - `ask` string, required: The question, as the person reads it.
      - `why` string, required: Why the script needs it.
      - `example` string, required: One example answer.
    - `questions_note` string, nullable: Say this to the person, in your own words, INSTEAD of asking anything — the questions did not save. Never ask a question from `questions` in the same turn you say this.
    - `state` 'confirmation_required' | 'written' | 'in_flight', required: written — the script is written and below; in_flight — it is still running: nothing failed, do not send it again, follow job_id with jobs.read; confirmation_required — a key with no member behind it asked first: nothing ran and nothing was charged.
    - `job_id` string: The job's handle. Read its status with `jobs.read` (REST: POST /api/v1/tools/jobs.read) until it says succeeded or failed.
    - `confirmation_id` string, uuid: Present only while confirmation is required.
    - `expires_in_seconds` integer: How long that confirmation stays usable.
    - `request_summary` string: Present only while confirmation is required — what will run, in one sentence, for a person to approve.
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/f9b4aeb83edc?raw)