Skip to main content
Glama

move

Reposition a shot in its current scene or transfer it into another scene while keeping all settings, with a single undo step.

Instructions

Move a shot to another position, in its own scene or into another scene. The shot keeps all its settings. One undo step for the person. Returns { done, shot }. To copy instead of move, use duplicate.

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": {
      "id": "<id>"
    },
    "name": "move"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe shot to move.
indexNoOr: its new position in the scene, from 0. Left out (and no before): the end.
sceneNoTarget scene id or index. Left out: its own scene.
beforeNoPut it before this shot id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the shot retains all its settings, that the operation collapses into a single undo step, and the return shape { done, shot }. The annotations already cover safety (destructiveHint=false), so this added context is a genuine bonus. It stops short of covering failure behavior, such as what happens with an invalid target scene or shot id.

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?

Four short sentences, front-loaded with the core action, then behavior, then return value, then the disambiguation pointer. Nothing is wasted and each sentence adds distinct information.

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 four-parameter mutation with no separate output schema, the description still supplies the return shape, the undo semantics, and the sibling alternative. An agent has everything needed to invoke this correctly.

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 description coverage is 100%, so the schema already documents id, index, scene, and before, including the defaults for index and scene. The description only implicitly gestures at the scene parameter ('its own scene or into another scene') and adds no syntax or precedence detail beyond what the schema states. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Move a shot'), plus the scope of the operation ('in its own scene or into another scene'). It also explicitly names the sibling it is not ('To copy instead of move, use duplicate'), so an agent can distinguish it from duplicate without opening either 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?

Names the explicit alternative (duplicate) and the condition that selects it (copying instead of moving). It also clarifies the two top-level modes of operation, within-scene repositioning versus cross-scene transfer, so no inference is needed to pick the right tool.

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