Reel Estate MCP

Official

Overview Schema Source Related Servers Discussions Admin

Retime a timeline element

move_timeline_element

Change the start time and duration of a timeline element to reposition floating audio or overlay elements in your video project.

Instructions

Change when a single timeline element starts and/or how long it lasts (any track). Use to nudge a floating audio/overlay element to a new point. To resequence all clips, use reorder_timeline. Element ids come from get_project (timeline.tracks[].elements[].id). Blocked in read-only mode.

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>",
      "elementId": "<elementId>"
    },
    "name": "move_timeline_element"
  }
}

Input Schema

Name	Required	Description
`duration`	No	New duration in seconds.
`elementId`	Yes
`projectId`	Yes
`startTime`	No	New start, seconds from the movie start.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Jul 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool is 'Blocked in read-only mode' and works on 'any track'. While it does not detail side effects like conflict handling, it transparently conveys a key constraint.

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?

The description is four sentences, each earning its place: purpose, usage guide, alternative, ID source, and behavioral note. No wasted words, well-structured.

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?

Given no output schema and no annotations, the description covers purpose, usage, parameter sourcing, and a key behavioral constraint. It omits error behavior but is otherwise complete for a mutation tool of moderate complexity.

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 50% (only duration and startTime have descriptions in schema). The description adds meaning by mapping 'starts' to startTime and 'how long it lasts' to duration, and specifies that elementId comes from get_project, compensating for undocumented parameters.

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?

The description uses a specific verb 'Change' and resource 'timeline element', clearly stating it adjusts start and/or duration. It distinguishes itself from the sibling tool 'reorder_timeline' by explicitly noting it works on a single element.

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?

The description advises when to use this tool ('nudge a floating audio/overlay element to a new point') and provides an explicit alternative ('To resequence all clips, use reorder_timeline'). It also indicates where to obtain required IDs ('Element ids come from get_project').

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