save_proposal
Save a proposal document for user review before implementing a complex project. The proposal MUST include a Models section listing the friendly names of the planned image/still and video models, a "💰 Estimated Cost" section with one estimated USD total and a spending ceiling for the planned project, and a concrete numbered scene/shot or beat list. Default project models are Nano Banana 2.1 (google-nano-banana-2-1) for character/location/shot still images and Gemini Omni 1.2 Flash (google-gemini-omni-1-2) for videos after still-image approval. Keep those raw IDs in tool arguments and use friendly model names in user-facing proposal text. Do not use source-file references such as "from script.md" or vague language such as "approximately X shots" instead of enumerating the planned work. Save the complete proposal but show only a short summary in chat, including models, cost and approval scope. Provide a View full proposal link using the returned reviewUrl and ask for approval or changes in chat. Use native question controls only when the host provides an approval-capable tool. Never require clicking approval in Sequencer or fabricate buttons. Open the link only when the user requests it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspaceId": "<workspaceId>",
"editId": "<editId>",
"proposalMarkdown": "<proposalMarkdown>"
},
"name": "save_proposal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| editId | Yes | The edit ID to save the proposal to | |
| threadId | No | Optional chat thread ID | |
| sourceMedia | No | Uploaded media from the original Spark request that must remain available after proposal approval | |
| workspaceId | Yes | The workspace ID | |
| productionPlan | No | Exact production jobs, starting-image media IDs, settings and per-job cost limits. Required for combined plan/image/budget approval. | |
| proposalSummary | No | Short user-facing summary, about 100 to 150 words: concept, runtime/format, shot count, visual/audio direction, friendly models, cost, uncertainty and approval scope. Full script and shot details belong in proposalMarkdown. | |
| proposalMarkdown | Yes | The full proposal content in Markdown format, including concrete numbered scenes/shots or beats. If based on a script or beat sheet, extract and enumerate the planned shots; do not merely reference the file. |