framesail

Render segments

render

Destructive

Render segment images and clips, the biggest spend in the video: always run it with dry_run=true first and get the user's yes on the estimate.

generate: without segment_numbers, everything not yet rendered (items rendering are skipped); with them, those segments, finished renders included, e.g. the first minute before the whole video. Overrides need segment_numbers and what=images or what=clips.

animate: turn one segment's rendered image into a clip; animate only images worth motion. dry_run quotes the default clip or talking head model. A refused render leaves the segment as it was; to go back to the image, segment_restructure change_type to=image keep_image=true.

Check renders with storyboard_read action=segment_assets and view_image.

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": {
      "action": "<action>",
      "project_id": "<project_id>"
    },
    "name": "render"
  }
}

Input Schema

Name	Required	Description	Default
`what`	No	generate: images (everything but clips: images, overlay segments, real photos, B-roll), clips, or all	all
`model`	No	Model id (get_generation_options); omit for the saved choice
`action`	Yes	generate: optional segment_numbers, what; animate: segment_number, optional talking_head
`dry_run`	No	Return the count and credit estimate; start nothing
`settings`	No	Model settings: keys of its settings_schema
`project_id`	Yes	Project id
`talking_head`	No	animate: true for a talking head (the person in the image speaks the narration with lip sync, billed on the segment's full length); false for a clip
`segment_number`	No	Segment number (1-based, from storyboard_read)
`segment_numbers`	No	generate: only these segments, finished ones included; omit for everything not yet rendered
`editable_sections`	No	Template prompt section overrides, keyed by section id

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructive=true/non-idempotent, but the description adds context the annotations cannot: this is 'the biggest spend in the video' (cost magnitude), dry_run returns a credit estimate, and a refused render 'leaves the segment as it was'. It also discloses that passing segment_numbers re-renders finished renders, which is exactly the destructive behavior an agent needs warned about.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the cost warning and the dry_run prerequisite before any mode detail, which is the right priority order. It is dense and fragment-heavy, but nearly every clause carries operational meaning; only the animate sentence's phrasing is slightly compressed at the cost of readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, no-output-schema mutation tool, the description covers the full call lifecycle: cost warning, required dry-run preflight, mode branching, override constraints, failure behavior, rollback path, and how to verify results. Nothing essential to calling it correctly is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine cross-parameter semantics the schema does not: omitting segment_numbers renders everything not yet rendered and skips in-flight items, whereas supplying it includes finished renders; overrides additionally require what=images or clips; dry_run quotes the default clip or talking head model. Only the less-used settings/editable_sections/model params get no extra narrative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Render segment images and clips') and immediately distinguishes the two modes it supports: generate and animate. An agent can tell this apart from siblings like storyboard_generate or assets_generate from the first clause alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mandatory workflow guidance ('always run it with dry_run=true first and get the user's yes on the estimate'), plus mode-selection rules (animate only images worth motion; overrides need segment_numbers and what=images or clips). It also routes the agent to alternatives for adjacent tasks: storyboard_read action=segment_assets and view_image to check renders, and segment_restructure to revert to an image.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All framesail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?