Use engine_docs first. The pinned contract requires code for engine_exec; engine_document requires action; and engine_export returns jobId on success.
- Ask for the document purpose, output format, and destination.
- Call
engine_execwithcodethat creates the minimum document content. - Call
engine_documentwithaction: "list"to confirm the created document and capture its returned identifier. - State the export target and request confirmation if the export writes or replaces a file.
- Call
engine_exportwith the published export arguments. - If it returns a job identifier, follow the async job example.
Synthetic identifiers, such as document_demo_001, show flow only. See the pinned tool contract for released input and result fields.