Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

scene.reorder

Move a scene to a new position among the project's scenes

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>",
      "expectedVersion": "<expectedVersion>",
      "sceneId": "<sceneId>",
      "newOrder": "<newOrder>"
    },
    "name": "scene.reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneIdYes
newOrderYes
projectIdYes
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and delivers almost nothing: it implies a mutation but says nothing about index shifting behavior on sibling scenes, whether the operation is atomic/batch, permission requirements, or error behavior on stale versions. The presence of an expectedVersion parameter signals a concurrency/optimistic-locking contract that the description never mentions.

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?

A single front-loaded sentence with no wasted words and an accurate scope qualifier. Its brevity is a virtue structurally, though it is brevity at the cost of information rather than achieved through efficiency.

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?

For a four-required-parameter mutation tool with no annotations, no parameter documentation, and no output schema, one sentence is far too thin. An agent cannot determine index conventions, whether reordering shifts other scenes, or how to satisfy the version guard.

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 0% and all four parameters are required, yet the description only loosely gestures at 'newOrder' via 'new position'. The critical semantics of expectedVersion (a version guard, not a plain integer) and the zero-based indexing implied by newOrder's minimum: 0 are left entirely undocumented.

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 ('Move') plus resource ('a scene') and scope ('among the project's scenes'), which cleanly separates it from scene.create/update/delete. It does not explicitly distinguish itself from nearby siblings like shot.reorder or track.reorder, but the resource noun makes the target domain 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?

No guidance on when to reorder versus using scene.update, no prerequisites, and no mention of what happens to the scenes in between. The agent must infer all invocation conditions from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CutClip.one toolsInspect
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.

Resources