CueFrame

New Composition

new_composition

Create a NEW composition (a new video) inside a project — a project is a workspace that holds many videos. Returns { compositionId, format, etag }. Pass an optional name and format (aspectRatio/fps/resolution); format defaults to the project's compositionFormat. The first composition becomes the project's active default. To author it, seed with apply_composition then compose({ fromComposition: true }) — your authored graphics ride as locked clips, carried verbatim; to render a specific one, pass its compositionId to create_render. (For a reframed sibling in another aspect, use derive_composition.)

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": {
      "projectId": "<projectId>",
      "body": "<body>"
    },
    "name": "new_composition"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	POST /projects/:id/compositions body — create a new video (composition) in the project. `format` defaults to the project's compositionFormat when omitted.
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.
`projectId`	Yes	projectId (path).

Output Schema

Name	Required	Description
`etag`	No	The strong ETag of the empty composition, for If-Match on its first write.
`format`	No
`compositionId`	No	The new composition's id: `composition_id` for apply_composition, `compositionId` for preview_frame and create_render.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 28, 2026

addedInput schema / $defs

Added value: +{
+  "__schema0": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "__schema1": {
+    "additionalProperties": {},
+    "properties": {
+      "aspectRatio": {
+        "enum": [
+          "16:9",
+          "9:16",
+          "1:1",
+          "4:5"
+        ],
+        "type": "string"
+      },
+      "fps": {
+        "anyOf": [
+          {
+            "const": 24,
+            "type": "number"
+          },
+          {
+            "const": 25,
+            "type": "number"
+          },
+          {
+            "const": 30,
+            "type": "number"
+          },
+          {
+            "const": 60,
+            "type": "number"
+          }
+        ]
+      },
+      "platform": {
+        "type": "string"
+      },
+      "resolution": {
+        "enum": [
+          "hd",
+          "fhd",
+          "4k"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "aspectRatio"
+    ],
+    "type": "object"
+  },
+  "__schema2": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / properties / body / properties / format / $ref
```
Added value: +"#/$defs/__schema1"
```
removedInput schema / properties / body / properties / format / additionalProperties
```
Removed value: -{}
```

removedInput schema / properties / body / properties / format / properties

Removed value: -{
-  "aspectRatio": {
-    "enum": [
-      "16:9",
-      "9:16",
-      "1:1",
-      "4:5"
-    ],
-    "type": "string"
-  },
-  "fps": {
-    "anyOf": [
-      {
-        "const": 24,
-        "type": "number"
-      },
-      {
-        "const": 25,
-        "type": "number"
-      },
-      {
-        "const": 30,
-        "type": "number"
-      },
-      {
-        "const": 60,
-        "type": "number"
-      }
-    ]
-  },
-  "platform": {
-    "type": "string"
-  },
-  "resolution": {
-    "enum": [
-      "hd",
-      "fhd",
-      "4k"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / body / properties / format / required
```
Removed value: -[
-  "aspectRatio"
-]
```
removedInput schema / properties / body / properties / format / type
```
Removed value: -"object"
```
addedInput schema / properties / body / properties / name / $ref
```
Added value: +"#/$defs/__schema0"
```
removedInput schema / properties / body / properties / name / maxLength
```
Removed value: -200
```
removedInput schema / properties / body / properties / name / minLength
```
Removed value: -1
```
removedInput schema / properties / body / properties / name / type
```
Removed value: -"string"
```
addedInput schema / properties / commandId / $ref
```
Added value: +"#/$defs/__schema2"
```
removedInput schema / properties / commandId / maxLength
```
Removed value: -128
```
removedInput schema / properties / commandId / minLength
```
Removed value: -1
```
removedInput schema / properties / commandId / type
```
Removed value: -"string"
```

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / commandId

Added value: +{
+  "description": "Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / body / properties / format / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "compositionId": {
+      "description": "The new composition's id: `composition_id` for apply_composition, `compositionId` for preview_frame and create_render.",
+      "type": "string"
+    },
+    "etag": {
+      "description": "The strong ETag of the empty composition, for If-Match on its first write.",
+      "type": "string"
+    },
+    "format": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 15, 2026
- removedInput schema / properties / body / properties / format / description
```
Removed value: -"Output-format spec per §Format."
```
- addedInput schema / properties / body / properties / format / properties / platform
```
Added value: +{
+  "type": "string"
+}
```
First observedOct 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the mutating, non-idempotent profile; the description adds substantive behavior: the return shape, that format defaults to the project's compositionFormat, that the first composition becomes the active default, and that authored graphics ride as locked clips carried verbatim. These are real side effects and data-flow facts an agent cannot get from the annotation flags.

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 core action and return shape, then workflow, then alternatives. Dense but every clause carries information; the trailing parenthetical is slightly cramped but useful.

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?

With an output schema, full schema descriptions, and annotations present, the description fills the remaining gap: the authoring workflow and the defaulting behavior. Nothing an agent needs to invoke this correctly appears missing.

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 meaning beyond field names: the name is optional, format is optional and falls back to the project's compositionFormat, and it summarizes the format facets (aspectRatio/fps/resolution). It does not explain commandId's retry semantics (that lives in the schema) or the platform field.

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?

Starts with a specific verb and resource ('Create a NEW composition (a new video) inside a project') and defines the parent concept. It explicitly separates itself from siblings by naming derive_composition for reframed variants and create_render for rendering.

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 an explicit workflow: seed with apply_composition then compose({ fromComposition: true }), then pass compositionId to create_render. It also states the alternative route ('For a reframed sibling in another aspect, use derive_composition'), leaving little to inference.

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

All CueFrame 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.