Workflows
Check progress and recover
Use the identifiers returned by creation to follow the original work. A progress check is read-only; another creation call is not a status check.
MCPIndividual and batch status
Call get_page_run with the returned PageRun public_id as run_id. The states are queued, running, succeeded, and failed. Use page_url only after success; retain failure_reason for failures.
Call get_enrichment with enrichment_uuid when you need every run in the batch. Mixed results are possible. Report successful URLs and failures separately.
Find ready Pages
Pages become available as processing completes. Follow individual Page statuses for ready links; completed Pages can be used while the rest of the batch continues.
crm_writeback_state, screenshot_state, and og_image_state describe separate work. A failed optional stage must not be reported as proof that no Page exists.
Recover deliberately
Correct the cause of a failed run before resubmitting the intended prospects. Required prompt errors need the Page owner’s definition and inputs checked.
For template-generation progress, use the distinct get_template_generation tool and its returned run_id. It recommends one-minute polling and has a different terminal state vocabulary.