generate_script

Inputs

{
  "type": "object",
  "properties": {
    "workspace_id": {
      "type": "string"
    },
    "script": {
      "type": "object"
    },
    "mode": {
      "type": "string",
      "enum": [
        "agent",
        "byo_key"
      ]
    },
    "parent_script_id": {
      "type": "integer"
    },
    "hook_type_lens": {
      "type": "string",
      "enum": [
        "informative",
        "engagement_bait",
        "disappointment_contrarian",
        "curiosity_gap",
        "stakes",
        "success_case_study",
        "failure_lesson",
        "question_open_loop",
        "frame_shift"
      ],
      "description": "Optional hook lens that biases the script's opening toward that style (generation intent)."
    }
  },
  "additionalProperties": false,
  "required": [
    "workspace_id"
  ]
}

Outputs and behavior

Prepare workspace grounding for a video script, or save an agent-written script as a new version. Use for a new draft; use revise_script to revise an existing script or write_blog/write_tweet for prose pieces. Omit script to retrieve context, then submit your structured draft. The agent writes it; server-side BYO generation is not implemented. Returns grounding or the saved script ID and version.

The registry does not publish an output schema for this tool. The description above is its documented behavior; response fields beyond it are not specified here.

Example call

Example tool name and arguments, generated from the input schema. Replace placeholder strings and sample numbers with your own values. This is a request template, not a recorded call or response.

{
  "name": "generate_script",
  "arguments": {
    "workspace_id": "YOUR_WORKSPACE_ID"
  }
}

Clients

This tool is available to MCP clients using stdio or http.

The registry records transport support, not individual client test results. See the MCP setup reference for named clients, configuration, and tool-list limits.