Cutscene

Create a film

create_film

Start a film on the user's account: from a template (recommended: it comes cut, with transitions, music and sounds), empty, or as a copy of one of its films (from: a film of its own with an id of its own, to try a variant without touching the original). Give the brand here or later with set_brand. The answer gives the film's id (prj_…), which every other tool takes, and the address it opens at in the editor; the film appears in « Mes films ».

Input Schema

Name	Required	Description
`from`	No	The id of a film of the account to copy (prj_…, see list_films): the copy keeps its shots, words, brand and format, and takes name (and title, when given) only
`lang`	No	Language of the example words (default en)
`logo`	No	null takes the logo away. A logo is put in by the user in the editor (open_in_editor gives the film's address): this connector reads no file of theirs
`name`	Yes	The film's title in « Mes films », e.g. Acme launch (title, when given, takes its place). The film itself is named by the id the answer gives
`site`	No	The product's public web address (https://monproduit.com). Cutscene reads it: the name, the logo, the colours and the fonts, and pictures of its home page and of up to two pages it links to (features, product), put in the shots that show a screen and still wait for a picture. Only a site the user has the right to use (their own product's). What you give besides (brand_name, colors, fonts, logo) wins over what the site says. The answer says what was found and what was not: ask the user for the rest
`fonts`	No	Font families of the library (see the guide resource for the list)
`title`	No	The film's title (default: name)
`colors`	No	bg = background, surface = cards, ink = text, muted = quiet text, accent = the brand's colour (key words, buttons), accent2 = a second colour (a word that turns on a ground of the brand's colour, a second dot). Left out, accent2 is a deep shade of accent
`format`	No	16:9 (default), 9:16, 4:5 or 1:1. Can change later: shots recompose themselves
`radius`	No	Corner radius of cards and screens: 4 sharp, 16 soft, 28 round
`montage`	No	A montage id (see list_montages), or a template people shared (search_community). Without one the film is empty
`product`	No	The product's name and tagline, used by the montage where it shows them
`brand_name`	No	The product's or company's name

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no output schema, the description carries the return-value burden well: it discloses that the answer contains the film id with its prj_ prefix that "every other tool takes", plus the editor address, and that the film appears in « Mes films ». It also clarifies that a copy is independent of its source and that site scraping reports what was found and what was not, telling the agent to ask the user for the rest.

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-loaded with the verb and the three modes, and every clause carries information. The nested parentheticals (especially the one inside the `from` explanation) make it denser than it needs to be, but nothing is padding.

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 13-parameter, nested-object tool with no output schema, the description covers the creation modes, brand routing, side effects and the return payload adequately. It leaves the many styling parameters (colors, fonts, radius) entirely to the schema, which is acceptable given the 100% coverage.

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?

With 100% schema description coverage, the schema already documents all 13 params, so the baseline is 3. The description adds genuine motivation beyond that: why to use `from` (a variant without touching the original) and why templates are recommended (cut, with transitions, music and sounds).

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?

States a specific verb and resource ("Start a film on the user's account") and enumerates the three creation modes: template, empty, or copy of an existing film. An agent can distinguish it from siblings like edit_film or create_piece without opening the schema.

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?

Recommends the template route explicitly, explains why one would use the copy route ("to try a variant without touching the original"), and routes brand setup to set_brand ("Give the brand here or later with set_brand"). It names alternatives but does not state any when-not-to-use condition.

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

All Cutscene 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?