CueFrame

Start from Template

start_template

Idempotent

Create a new project from a catalog or org template. The server prepares media and verified mattes before the project is ready. Pass the returned jobId to wait_job(kind="template").

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": {
      "template": "<template>",
      "projectName": "<projectName>"
    },
    "name": "start_template"
  }
}

Input Schema

Name	Required	Description
`media`	No
`preset`	No
`values`	No
`template`	Yes
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.
`brandKitId`	No
`projectName`	Yes
`idempotencyKey`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / commandId / $ref
```
Added value: +"#/$defs/__schema0"
```
- 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"
+}

First observedOct 10, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (not read-only, idempotent, non-destructive, closed-world), and the description adds real value on top: the operation is asynchronous and the server prepares media and verified mattes before the project is ready. That explains why a jobId is returned and why waiting is required. It stops short of saying what happens on failure or whether partial projects are cleaned up.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero filler, with the core action front-loaded and the async continuation immediately after. Nothing redundant is included.

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

Completeness2/5

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

There is no output schema, yet the description only says a jobId is returned while omitting any other return content. With 8 parameters, nested objects, and 13% schema coverage, an agent cannot determine how to supply media or template values from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% of 8 parameters (only commandId is documented in-schema), so the description must compensate and largely does not. It implies the existence of a template parameter ("catalog or org template") but never explains projectName, media mapping, preset, values, brandKitId, or idempotencyKey semantics. For a tool with nested media objects supporting three shapes (mediaId / url / sample), this silence is a significant gap.

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: "Create a new project from a catalog or org template." That is clearer than the name alone and hints at the two template sources. It does not, however, distinguish itself from close siblings like create_project or apply_template, so an agent must still infer which path creates a project from a template.

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

Usage Guidelines3/5

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

The description gives the follow-up workflow ("Pass the returned jobId to wait_job(kind=\"template\")"), which is genuinely useful routing guidance. But it never says when to choose this over create_project or apply_template, nor any prerequisites (e.g., that a template must exist, or what preset/values do).

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.