CueFrame

Cancel Export

cancel_export

Idempotent

Cancel an in-flight NLE export (fcpxml/premiere). Needs projectId + exportId (from the export enqueue). No-op-reject (422) if already terminal.

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>",
      "exportId": "<exportId>"
    },
    "name": "cancel_export"
  }
}

Input Schema

Name	Required	Description
`exportId`	Yes	exportId (path).
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.
`projectId`	Yes	projectId (path).

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

A4.4/5.0

Behavior4/5

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

Annotations already cover safety (non-read-only, non-destructive, idempotent), but the description adds the terminal-state 422 rejection, which is behavior not encoded anywhere in the structured fields. It omits what a successful cancel returns, though with no output schema that is a small gap.

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 clauses, no filler: action+scope first, required inputs second, failure mode last. Every sentence carries information the agent needs.

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?

For a low-complexity, 3-parameter mutation tool with a fully-described schema and no output schema, this covers the action, prerequisites, and the one surprising error case. Only the success response shape is unaddressed, which is minor here.

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 slightly beyond by naming exactly which two ids are required and where exportId comes from ('from the export enqueue'), giving the agent provenance the bare 'exportId (path)' schema description lacks.

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+resource: 'Cancel an in-flight NLE export (fcpxml/premiere)'. The scope qualifier 'in-flight' and the format parenthetical distinguish it from the many sibling cancel_* tools (cancel_compose, cancel_job, cancel_render) without the agent opening a 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?

The 'in-flight' qualifier plus 'No-op-reject (422) if already terminal' tells the agent the precondition for calling and what happens if it guesses wrong. It does not explicitly point at the sibling alternatives (cancel_render vs cancel_job), so the routing is inferred rather than stated.

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.