CueFrame

Update Project

update_project

Destructive

Update a project's mutable fields (e.g. name, format, brandKitId). Pass projectId + the changed fields as body. Setting brandKitId binds/changes the project brand kit so every render of this project themes from it. Returns the updated ProjectResponse.

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": "update_project"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	PATCH /projects/:id body.
`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
`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.

Changed19 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": {
+    "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 / 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/__schema4"
```
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"
+}

Changed1 schema field changedOct 18, 2026
- changedInput schema / properties / body / properties / format / additionalProperties
```
Previous value: -falseNew value: +{}
```
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

B3.3/5.0

Behavior3/5

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

The description adds real context beyond annotations: brandKitId binds the project brand kit so every render re-themes, and a partial-update semantics is stated. However, annotations declare destructiveHint=true and idempotentHint=false, and the description never says what a destructive update might overwrite (e.g. do omitted fields get reset? does changing format invalidate renders?) or that retries need commandId — that fact lives only in the schema.

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?

Four compact sentences, front-loaded with the action and the required inputs, followed by the one non-obvious field effect and the return type. No filler, though the final return-value sentence is partly redundant given the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the output schema and a one-line mention, so that is fine. What is missing for a destructive, non-idempotent mutation is any note on side effects (render invalidation, partial-vs-full body semantics, retry safety via commandId), which leaves the agent to infer risk from annotations alone.

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 earns a notch more by explaining the effect of one parameter (brandKitId rewrites theming on all renders) and clarifying that body carries only the changed fields, which the schema's PATCH note implies but does not spell out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update a project's mutable fields') and enumerates the mutable fields, which clearly distinguishes it from update_component/update_brief/update_webhook by resource. It stops short of explicitly naming an alternative, but the resource scoping makes the target unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus create_project, update_component, or whether changing `format` invalidates existing compositions/renders. The only implied usage is 'pass projectId + changed fields', which is invocation mechanics, not selection guidance.

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.