Skip to main content
Glama

Save a render to your private space

save_render
Destructive

Save the video you just rendered to the user’s private Launchscene space, with the brief and the Launchscene references it was built from. Call it once the file exists, and again with project_id for each later version of the same film. Returns a one-use upload command to run once with the real file path (MP4 or WebM, 100 MiB and 180 seconds maximum); the file is then kept in the project and measured against its reference on its own. Private to the account: never published, never added to the library. Give the user the returned project.url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat changed in this version, in one or two sentences.
agentNoThe tool that built the video, for example "Claude Code", "Codex" or "Cursor".
briefNoThe brief this video was built from, as written for the build. Stored privately with the project.
titleNoProject name, usually the product and the film ("Acme launch film"). Names a new project, or renames an existing one.
compare_toNoSlug of the published Launchscene video to measure this version against. Defaults to the film of the first reference, then to the one used for the previous version.
project_idNoAn existing project of this account, to add the next version to it. Omit to start a new project.
referencesNoLaunchscene scene ids and/or video slugs this video was built from, most important first.

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses privacy scope, the two-step upload handshake ("a one-use upload command to run once with the real file path"), accepted formats and hard limits (MP4 or WebM, 100 MiB, 180 seconds), and that the file is retained and measured against its reference. The gap is the destructiveHint=true annotation: nothing explains what a save can overwrite or destroy, nor that repeated calls are non-idempotent version appends.

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?

The opening sentence front-loads the action and destination, and every later clause (timing, upload handshake, limits, privacy, returned URL) carries distinct information. It is dense and packs several clauses plus a parenthetical into one long sentence, which costs a little readability.

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?

With an output schema present, the description need not detail return values, yet it usefully calls out the one-use upload command and instructs the agent to surface project.url. What is missing is any statement of what the destructive flag means in practice or what permissions/account state are required.

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; the description goes further by tying parameters into a workflow — project_id selects append-to-existing vs. new project, and the brief plus Launchscene references are stated as being carried along and stored privately. It does not add format or constraint detail for compare_to or references beyond what the schema already documents.

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?

"Save the video you just rendered to the user's private Launchscene space" names a specific verb, resource and destination, and the privacy clause ("never published, never added to the library") separates it from publishing/board siblings such as save_to_board. An agent can tell what this does and where the artifact lands 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?

Timing is explicit: "Call it once the file exists, and again with project_id for each later version of the same film," which resolves the main ambiguity (new project vs. new version). It does not name a sibling alternative or state when to prefer something else (e.g., create_render_upload), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources