CueFrame

Create Project

create_project

Create a new project — the unit you compose and render into. compose / apply_composition / create_render / the preview family all require a projectId; this mints one. Pass name (required) plus optionally a format (aspectRatio/fps/resolution) and brandKitId. brandKitId binds a brand kit to the PROJECT (pass the kitId from create_brand_kit): colors/fonts/motion theme every render of this project automatically (omit it and the output is unbranded). Bind or change it later via update_project (PATCH /projects/:id over REST). Returns the ProjectResponse (id + metadata).

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

Input Schema

Name	Required	Description	Default
`body`	Yes	POST /projects body.
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.

Output Schema

Name	Required	Description
`id`	No
`name`	No
`format`	No
`webUrl`	No	A browser URL that opens THIS project, or null when CueFrame exposes no web view for a project. Null today: the console serves account surfaces (keys, usage, billing) and has no per-project page, so there is no link to give. Do NOT synthesise one — a guessed console path 404s. Show the user rendered output (create_render → outputUrl) or a preview still instead. This field becoming non-null is the signal that a real project view exists.
`createdAt`	No
`brandKitId`	No
`lastRender`	No	Most recent render for a project, if any.
`composition`	No	Summary of a project's stored composition.
`description`	No
`activeCompositionId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedOct 28, 2026

addedInput schema / $defs

Added value: +{
+  "__schema0": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "__schema1": {
+    "type": "string"
+  },
+  "__schema2": {
+    "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"
+  },
+  "__schema3": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "__schema4": {
+    "deprecated": true,
+    "exclusiveMinimum": 0,
+    "type": "number"
+  },
+  "__schema5": {
+    "deprecated": true,
+    "exclusiveMinimum": 0,
+    "type": "number"
+  },
+  "__schema6": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / properties / body / properties / brandKitId / $ref
```
Added value: +"#/$defs/__schema3"
```
removedInput schema / properties / body / properties / brandKitId / minLength
```
Removed value: -1
```
removedInput schema / properties / body / properties / brandKitId / type
```
Removed value: -"string"
```
addedInput schema / properties / body / properties / description / $ref
```
Added value: +"#/$defs/__schema1"
```
removedInput schema / properties / body / properties / description / type
```
Removed value: -"string"
```
addedInput schema / properties / body / properties / format / $ref
```
Added value: +"#/$defs/__schema2"
```
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 / height / $ref
```
Added value: +"#/$defs/__schema5"
```
removedInput schema / properties / body / properties / height / deprecated
```
Removed value: -true
```
removedInput schema / properties / body / properties / height / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / body / properties / height / type
```
Removed value: -"number"
```
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 / body / properties / width / $ref
```
Added value: +"#/$defs/__schema4"
```
removedInput schema / properties / body / properties / width / deprecated
```
Removed value: -true
```
removedInput schema / properties / body / properties / width / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / body / properties / width / type
```
Removed value: -"number"
```
addedInput schema / properties / commandId / $ref
```
Added value: +"#/$defs/__schema6"
```
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"
+}

Changed3 schema fields changedOct 18, 2026
- changedInput schema / properties / body / properties / format / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / body / properties / height / deprecated
```
Added value: +true
```
- addedInput schema / properties / body / properties / width / deprecated
```
Added value: +true
```
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.1/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false). The description adds genuinely useful behavior — brandKitId propagates colors/fonts/motion theme to every render of the project, and omitting it yields unbranded output — plus the return type. However, it is silent on the deprecated width/height fields and on what happens if format conflicts with them, which is the main behavioral risk here.

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 purpose, then prerequisite role, then parameters, then return value — a sensible order with no filler sentences. The parenthetical '(PATCH /projects/:id over REST)' is slightly extraneous transport detail for an MCP caller, but it does not obscure the guidance.

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?

An output schema exists and the description still names ProjectResponse (id + metadata), so return semantics are covered; creation effects and the brand-kit binding are explained. The remaining gap is the undocumented deprecated width/height pair, which an agent could plausibly pick from the schema without knowing the description's preferred format object.

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?

Schema description coverage is 100%, so the schema already documents both top-level parameters and the nested format object; baseline is 3. The description does add real value for brandKitId by tying it to create_brand_kit's kitId and spelling out the consequence of omission, but it never mentions the deprecated width/height fields or the free-form description 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?

States a specific verb and resource ('Create a new project') and immediately defines what a project is ('the unit you compose and render into'), which distinguishes it from compose, create_render, and the preview siblings that consume a projectId rather than mint one.

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?

Explicitly names the tools that require a projectId (compose / apply_composition / create_render / the preview family) and states this tool mints one, so the prerequisite relationship is unambiguous. It also routes the agent to update_project for later brand-kit changes, covering the obvious follow-up case.

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.