generate_storyboard
Plan the full visual storyboard: segments, shot pacing, image/video prompts, overlays, continuation chains — driven by the channel's director and art styles. Requires voiceover to exist (timing comes from it). BEFORE calling: confirm the project's asset_mix with your user (image vs video vs gener...
This record as markdown: /tools/com-framesail-framesail/generate-storyboard.md
What generate_storyboard does on Framesail
AI agents use generate_storyboard to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Model ID to plan with; empty uses the default (see list_models("storyboard")) |
settings | object | — | Model-specific settings; valid keys come from the model's settings_schema in list_models("storyboard") |
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
editable_sections | object | — | Per-call prompt section overrides, keyed by section name; see get_section_template("storyboard") |
Parameters from the server's own tool schema.
Why generate_storyboard is rated Medium
The tool creates new structured data (storyboard configuration) that modifies the project state and drives later rendering stages. While it doesn't execute the actual video rendering or delete anything, it is a generative/creative write operation that produces artifacts used by subsequent pipeline steps.
From the tool's definition Tool 'generates' and 'plans' a storyboard with segments, shot pacing, prompts, and overlays. The description states it creates visual planning artifacts (segments, shot pacing, image/video prompts, overlays, continuation chains) that structure downstream…
Attacks that exploit this kind of access
The rule that runs generate_storyboard safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_storyboard, this is the rule to start with:
generate_storyboard stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every generate_storyboard call is checked against it from then on.
Questions about generate_storyboard
Plan the full visual storyboard: segments, shot pacing, image/video prompts, overlays, continuation chains — driven by the channel's director and art styles. Requires voiceover to exist (timing comes from it). BEFORE calling: confirm the project's asset_mix with your user (image vs video vs generated_graphic percentages, update_project) — the storyboard plans against it and video-heavy mixes multiply the later render cost. Async — returns {job_id}; this is the longest LLM step. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_storyboard accepts 4 parameters: model, settings, project_id, editable_sections. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for generate_storyboard: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Framesail. Nothing to install.
generate_storyboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_storyboard rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for generate_storyboard. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
generate_storyboard is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue