framesail

Export the video

export_video

Destructive

Render the finished video from the editor timeline; free. When the export job completes, get_status carries export_url.

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

Input Schema

Name	Required	Description	Default
`project_id`	Yes	Project id

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / project_id / description

Previous value: -"Project ID, as returned by create_project or list_projects"New value: +"Project id"

removedInput schema / properties / project_id / title
```
Removed value: -"Project Id"
```
removedInput schema / title
```
Removed value: -"export_videoArguments"
```

Changed1 schema field changedJul 9, 2026
- addedInput schema / properties / project_id / description
```
Added value: +"Project ID, as returned by create_project or list_projects"
```
First observedJul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely non-derivable context: the operation is free and is asynchronous, with the result available via get_status's export_url. It doesn't warn about overwriting an existing export, but that is largely implied by the destructive annotation.

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

Conciseness5/5

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

Two tight sentences, the core action front-loaded, with the follow-up step immediately after. No filler.

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

Completeness4/5

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

For a single-param async job tool with no output schema, the description supplies what matters: it's asynchronous and the result is retrieved via get_status. The only gap is not distinguishing it from the 'render' sibling.

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

Parameters3/5

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

Only one parameter (project_id) and schema description coverage is 100%, so the schema already carries the semantics. The description adds nothing about the parameter, which is acceptable at this baseline.

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

Purpose4/5

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

States a specific verb+resource ('Render the finished video from the editor timeline'), which is clear and actionable. However, it does not differentiate itself from the sibling tool 'render', leaving the agent to infer the distinction between the two.

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

Usage Guidelines4/5

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

'free' gives a cost signal, and the second sentence tells the agent what to do after the job completes (poll get_status for export_url), which is concrete usage guidance. It stops short of saying when not to use it or how it differs from 'render'.

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?