| name | verification |
| description | Use when checking whether agent edits made through the Local Video Editor MCP are reflected in the project and timeline. |
Verification (Local Adaptation)
Prefer two signals:
- Staged
local-video-editor_read_project discovery for structure: timeline tracks, one track's items and placement, asset library, or targeted item/asset detail.
- A visual capture path for rendered evidence at exact frames.
Frame Extraction
ℹ️ Local FFmpeg pipeline: view_timeline_frames and view_asset_frames now use local FFmpeg instead of cloud Lambda. Frame extraction runs on your machine and returns paths to extracted frame images — no network hop, no signed URLs.
Composed timeline frames (view_timeline_frames)
Use local-video-editor_view_timeline_frames for composed timeline proof. This verifies the edited timeline: trims, layers, captions, effects, markers, placeholders, crops, transitions, and layout.
{
"timelineId": "<timeline-id>",
"frames": "30,45,75"
}
Returns paths to extracted frame images. Inspect them with the native image-reading tool.
Source asset frames (view_asset_frames)
Use local-video-editor_view_asset_frames for raw source-asset frame inspection:
{
"assetId": "<asset-id>",
"sourceTimesMs": "0,5000,10000"
}
Returns frame image paths extracted directly from the source asset via FFmpeg.
Direct local file inspection
If you have the original local file path (e.g., sourcePath from import), inspect that file locally with ffprobe / ffmpeg and your normal image-read flow. Prefer this over view_asset_frames for files you already have local access to.
Verification Workflow
Useful checks
| Scenario | Command |
|---|
| After import | local-video-editor_read_project({ "assetId": "<prefix>" }) |
| After move/trim | local-video-editor_read_project({ "itemId": "<prefix>" }) or discover track with view:"timeline", then view:"track" |
| After visual overlay or MG | local-video-editor_view_timeline_frames({ "frames": [30, 45, 75] }) |
| After user-requested source selection | Extract stills locally with ffmpeg from the source file |
Frame verification details
- When extracting frames, pass multiple frames in one call — settled state appears alongside any transient mid-animation frames.
- Compare frames before concluding: apparent truncation, missing elements, or broken design visible in only some of the batch may be animation, not a real flaw.
- If unclear, re-capture more frames around the suspect one before adjusting anything.
- Judge from the settled frames.
What to check in a settled frame
- Face/head is clear and unobstructed
- Important objects and gestures are visible
- Caption zone is clear when relevant
- MG is fully visible
- MG content is correct
- Text is legible
- No readable text overlaps
- Composition feels balanced and intentional
If verification fails
Classify the gap before changing tools:
- tool description or schema was insufficient
- skill instructions were missing a step
local-video-editor_read_project did not expose enough state- media/transcription pipeline failed
- local FFmpeg pipeline blocked
Frame Rate
When talking about seconds, verify the fps from local-video-editor_read_project or use adapter tools that resolve fps internally.
When reporting a timeline item location, use only the latest targeted item detail or view:"track" response for track alias, item id, start, duration, and asset id. Do not infer placement from orientation summary or previously read data.
