How to list Medux tasks with Medux MCP

Codex prompt pattern

In this workspace, use medux_list_tasks through Medux MCP to list Medux tasks.
First inspect and identify the intended account context and any status, pagination, or filter settings.
Show me the exact tool arguments before execution.
After the task completes, return the matching task records and verify that the response uses the intended filters and account context.

Approval gate

Before approving the call, compare the selected tool, file or asset IDs, ordering, timing, and output settings with the request. If a local filename was mapped to an uploaded Medux file ID, keep that mapping visible so it can be audited later.

Result verification

Let Codex monitor an asynchronous task until it reaches a terminal state, then save or report the matching task records. The final check is explicit: confirm that the response uses the intended filters and account context.

Claude prompt pattern

Using the assets and requirements in this conversation, help me list Medux tasks with Medux MCP.
Restate which input fulfills each role: the intended account context and any status, pagination, or filter settings.
Propose the medux_list_tasks call and summarize its arguments before asking for approval.
When it finishes, return the matching task records with a checklist confirming that the response uses the intended filters and account context.

Context checkpoint

Have Claude summarize the intended transformation, identify every source asset by role, and list the important constraints. Review that summary together with the proposed tool arguments; correct the conversation first if a file, order, time range, or setting is ambiguous.

Result verification

Keep the Medux task ID in the conversation while Claude checks progress. When processing ends, ask for the matching task records plus a concise validation checklist confirming that the response uses the intended filters and account context.