harmonize_series

What it does

The fix for visible seams in an orthomosaic (Pix4D, Metashape, WebODM) when clouds or the sun changed the light between frames, for timelapse flicker, and for uneven exposure across an event set. Each photo keeps its own grade; harmonize adds small Exposure, Temperature and Tint offsets (ordinary sliders, so exports and the Lightroom XMP handoff carry them) so that overlapping or consecutive frames match. mode "auto" uses GPS neighbours when the photos carry GPS (footprint overlaps from DJI altitude, yaw and focal length when present) and capture order otherwise; "gps" or "sequence" force one; "off" removes a previous harmonize. strength 0..100 scales the offsets. smoothness 0.1..10 (default 1): higher also evens out slow changes across the whole set, lower only removes frame-to-frame jumps. dry_run=true reports without writing. Re-running replaces, never stacks. Returns per-photo offsets plus seam scores before and after (RMS brightness and colour mismatch across overlaps, in stops; under about 0.05 is invisible). Big sets return {"status": "running", "job_id"}: poll get_job_status. Pair with preview_mosaic to look at the result.

Parameters

Asking for it

You do not call this by name. You say what you want, and the agent picks the tool:

Point imagic at my shoot and tell me what you find.

The rest of the editing tools

Where it runs

On your machine. imagic's MCP server is a local process that your AI client starts; the photos never leave your disk and nothing is uploaded. That is true of every tool in the reference, including this one.

To call it you need an MCP client connected to imagic. Setup takes about three minutes for Claude Code, Cursor, VS Code, Codex, Gemini CLI and ten others.