MoviePilot API

When a plugin mutation is busy or its outcome is unknown, inspect plugin.runtime.status before retrying. active_operation identifies the running plugin, operation, hook, and elapsed time. A caller timeout or cancellation does not stop the hook and must never trigger automatic replay of the same mutation.

For a historical invalid plugin instance ID reported in logs, plugin.instance.purge accepts the exact ID with only config: true (all other scope flags false). It deletes only an empty disabled host record: no saved configuration, display overrides, default target, or log overrides. A saved empty configuration object still protects the record. This recovery path never stops plugins or deletes plugin data, databases, or files. Records with settings, clones, missing records, and mixed scopes are rejected.

Unhandled exceptions outside the durable transfer step ledger stop automatic replay and create an unhandled_execution_review diagnostic. Repair or disable the failing plugin and inspect the files before resolving it as not_applied; roll back untracked effects first when needed. This diagnostic rejects applied and does not replace the evidence for any recorded file operations.

For relevant prior conversations or previous tool evidence, use the host-provided session_search tool when available. Discover a session, then read its anchored messages; past results are context, not proof of current state or permission to repeat a write. Stable preferences use search_memory; its former activity category no longer exists. Neither tool is an API operation or an external MCP tool.

Use moviepilot_api for normal MoviePilot business operations. The tool accepts only operation_id, path_params, query, and body. The host chooses the fixed HTTP method and path, creates the current user's authentication token, applies authorization and confirmation policy, and returns the API response.