Use FilmCraft in your agent’s chat
- Connect once. Follow the MCP setup instructions to add all 13 toolsets to your agent.
- Provide the file. Give your agent a path it can read, or attach the file if your client supports uploads. The agent needs file access and HTTP transfer tools.
- Describe the task. In your agent’s chat, say which file to use, what to do and what result you want. Your agent calls the connected tool and returns the information or output file.
What to ask your agent
After connecting, replace the example filename with your own file and send this in your agent’s chat:
Cut promo.mp4 from 2 seconds to 6 seconds and return the MP4.
No special command or required brand phrase. If your agent chooses another method, ask it to use the connected EasyRunCraft tools. Review the result before continuing.
Supported operations
Use editor_capabilities with editor: "film" to check supported operations. Pass the selected operation to process_film.
inspect- Read the clip’s duration, dimensions, frame rate, video codec and audio streams.
render_frame- Export a PNG at a specified timestamp in seconds.
trim_video- Export an up to eight-second range as H.264 MP4 with the clip’s audio when present. The output long edge is capped at 960 pixels.
Files, limits and results
Your assistant uses create_upload and sends the bytes to the upload URL with HTTP PUT. It then calls process_film with the uploaded file ID and a new request_id. Reuse the request ID only to retry the same request.
Each input and output file can be up to 20 MB for accounts without a subscription and Starter, or 100 MB on Creator and Studio. See plan file limits. Each account can have two active jobs and each native command has a 45-second limit. Frame and trim jobs accept one clip up to 120 seconds, 1920 by 1080 pixels in either orientation and 60 fps. The container must have a readable MP4 or QuickTime file type box.
Poll get_job at most once per second. Inspection data is in result; downloadable outputs are in file. Edits create a private copy. Open the FilmCraft editor.
Files and jobs expire after 24 hours. Upload and download links expire after 10 minutes. Anyone holding a valid link can use it until it expires.
Tool-call example for agents and developers
Your agent handles the tool calls. For a direct integration, the arguments to process_film look like this:
{
"file_id": "<uploaded file ID>",
"request_id": "<new request ID>",
"operation": {
"type": "trim_video",
"start": 2,
"end": 6
}
}Unsupported requests and feedback
Unsupported operation IDs return UNSUPPORTED_OPERATION. A supported operation can still fail on a particular file. Check the job's error before retrying.
Tell us what you wanted to do and what the assistant reported. You can include the task ID. Keep private files, signed links and access tokens out of the message.
Email FilmCraft feedback