CueFrame

Repin Component

repin_component

Move clips stored in a retired form to their native (version 4) successors: a clip pinning a retired TSX (version 3) component, or one stored before execution pins (needsUpgrade kind unpinned-component), moves to the successorSourceVersionId that get_composition's needsUpgrade (or a component_source_retired refusal) names. Pass projectId and, in body, optional clip_ids (omit them to move every clip that has a successor) and composition_id (the active composition when omitted). Saved inputs are kept. The answer lists moved and withoutSuccessor; rebuild the latter as native components (create_component, then apply_composition at the same timing and placement). A retired clip with no successor must be rebuilt or removed in the same write that upgrades the others: a write never leaves one in place.

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

Input Schema

Name	Required	Description
`body`	Yes
`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
`moved`	No
`inputsRefused`	No	Clips whose successor refuses their stored inputs (its input schema), each with why: fix the inputs by rebuilding the clip, or remove it.
`withoutSuccessor`	No	Clips in a retired form no curated release recorded: rebuild them as native components, or remove them, in the same edit that upgrades the others.

Schema Changelog

Changes observed during successful MCP inspections.

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

addedInput schema / properties / body / example
```
Added value: +{}
```

addedOutput schema / properties / inputsRefused

Added value: +{
+  "description": "Clips whose successor refuses their stored inputs (its input schema), each with why: fix the inputs by rebuilding the clip, or remove it.",
+  "items": {},
+  "type": "array"
+}

changedOutput schema / properties / withoutSuccessor / description

Previous value: -"Clips pinning a retired TSX source no curated release shipped: rebuild them as native components."New value: +"Clips in a retired form no curated release recorded: rebuild them as native components, or remove them, in the same edit that upgrades the others."

AddedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare it is a non-readOnly, non-destructive, non-idempotent write. The description adds real behavioral context beyond that: saved inputs are preserved, the response partitions results into moved and withoutSuccessor, and a write must never leave a retired clip in place. It does not fully spell out atomicity/permission requirements, so it is strong but not exhaustive.

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?

Information-dense and front-loaded: the operation and target come first, defaults and the withoutSuccessor follow-up after. The opening sentence is a long compound clause chain, but every clause carries usable meaning rather than filler.

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?

For a 3-parameter mutation with an output schema and annotations present, the description covers the trigger condition, parameter defaults, preserved state, the withoutSuccessor remediation path, and the invariant that no retired clip survives the write. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 67% and the schema already documents clip_ids (omit to move every clip with a successor), composition_id (active when omitted), and commandId retry identity. The description largely restates those defaults and adds no format, ordering, or edge-case detail beyond the schema, so baseline 3 applies.

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 (move) and resource (clips stored in a retired form) with the exact target (successorSourceVersionId of native version-4 components). It names the distinguishing conditions (unpinned-component needsUpgrade, component_source_retired refusal) and routes away from get_composition/create_component/apply_composition, so an agent can identify it without opening the schema.

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 explicit when-to-use: a clip pinning a retired TSX v3 component or one stored before execution pins, as flagged by get_composition's needsUpgrade or a component_source_retired refusal. It also states what to do for the no-successor case (rebuild via create_component then apply_composition) rather than leaving the alternative 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.