How ReelMy plans an edit

When you tell ReelMy "cut this to 45 seconds and make it punchy," it doesn't run one giant model and pray. It works the way a good editor works: it reads the material, writes a plan, executes a sequence of tools, and reviews the result before it hands anything back.

A timeline mid-edit

Step 1 — Understand

Before it touches a frame, ReelMy transcribes the audio, watches the video, and reads your brand kit. It knows what's on screen, who's talking, and what your channel's rules are — hook in the first 1.5 seconds, captions bottom-safe, always keep the intro sting.

Step 2 — Plan

Then it writes a plan: a short list of tool calls, each checked against your guidelines. You can watch it happen in the runtime — every call is a real, reversible step, not a black box.

❯ cut this to 45s and make it punchy
  planning — 4 tool calls across 2 servers
  → mcp:reelm.smartCut   { target: "0:45" }   ✓ 12 cuts
  → mcp:reelm.captions   { style: "pop" }      ✓ styled
  → skill:cinematic-grade                      ✓ applied
  → mcp:reelm.export     { ratio: "9:16" }     ✓ rendered
  ✓ done in 38s — verified & ready to review

Step 3 — Act, then verify

Each tool runs on the timeline exactly as if you'd done it by hand. When the pass is complete, ReelMy re-watches the result against your original request and fixes anything that drifted — a caption that overlaps the action, a cut that lands a beat too early.

Why MCP matters

Because ReelMy speaks Model Context Protocol both ways, the same agent runs inside ReelM and inside your own stack — Claude Code, Cursor, or a custom CLI. Your tools become tools ReelMy can call, and ReelM's tools become tools your agent can call. Learn more on the ReelMy page.

WRITTEN BY

Ahmad Fozooni

Founder · ReelM