get_job_status

What it does

scan_directory, analyze_photos, reanalyze_stale_photos, export_photos, and learn_style_from_library each dispatch as a background job on a remote connection when they cannot finish within that call's own budget, returning {"status": "running", "job_id": ...}. Call this with that job_id to keep checking: it waits up to wait_seconds (capped at 30) for the job to finish before answering, so a short loop of calls is enough to follow it to completion. Once finished it returns exactly what the original tool call would have returned. Only one long job runs at a time; while one is running, other tools answer {"status": "busy", ...} instead of their normal result. Local (stdio) clients can use this too, but their long tools always finish synchronously, so there is normally nothing to poll.

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 library 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.