Social Carousel Workflow
The exact designgen_carousel call sequence for a multi-slide social carousel, from plan to finished gallery.
Call sequence
Always start with operation start. Do not call designgen_generate in a loop to build a carousel.
- 1. designgen_carousel { "operation": "start", "campaignBrief": "...", "slideCount": 6, "aspectRatio": "4:5" } — plans the carousel and normally returns an approval (approvalCard when the client renders MCP Apps UI).
- 2. Present the quality, generation, and budget choices to the user. Never choose for them.
- 3. designgen_approvals { "operation": "decide_card", "approvalId": "<id>", "decision": "approve", "runNow": true, "generate": true, "qualityTier": "ultra", "maxCredits": 40 } — submits the decision. A generate-now decision needs a positive maxCredits that covers the estimate; use plan-only (generate: false or maxCredits: 0) otherwise.
- 4. designgen_carousel { "operation": "wait", "sessionId": "<sessionId from step 3>" } — or call exactly the nextCall the previous step returned. If the result includes another nextCall, call it again automatically; do not ask the user to poll.
- 5. Present the finished gallery (inline previews plus full-resolution links) once the wait result is terminal.
Recovering
If the approval card is missing or stale, do not retry designgen_carousel with the same arguments.
- approval_required with no live approvalId, or a connection mismatch: refresh the MCP connection and call designgen_carousel operation start again to regenerate the approval.
- Use designgen_approvals operation get to confirm an approval is still pending before presenting its controls as live.
- Use designgen_carousel operation status for a non-blocking progress check instead of wait when you do not want to block on completion.