regenerate_cast_portrait

Redraws ONE cast member's portrait - the same character, a new image - and attaches it to that member. Costs ONE image generation, not a new cast. WHEN: the user looked at the portraits and dislikes a specific member's face, or a member's portrait FAILED to generate (the story create refuses an episode whose cast has a failed portrait and names this). character_id is that member's id from generate_cast_portraits or list_characters (kind cast_member). THE CARD: this call has ALREADY put the aicut cast card in front of the user with this ONE member on it - the new face fills itself in as it generates, and the card carries the same download and the same review actions the full roster's card does. So do NOT call show_generation on the portrait, and do NOT poll: no get_image or wait_for_generation loops. ONE read is not a loop - if the user asks how it is doing, read portrait_image_id once with get_image and say what it says. IF YOU CANNOT RENDER AN AICUT CARD - a terminal, a plain SDK client, anything that did not negotiate the MCP Apps UI extension - no card appeared, so poll portrait_image_id with wait_for_generation (media image) and give the user the portrait url yourself. aicut cannot see which clients render cards and sends the same answer to all of them. AFTER: returns portrait_image_id with portrait_status: "generating". The member now points at the new portrait; the old one stays in the account's images. Repeat if they still dislike it - each repeat is one more portrait's price, which you state each time. WHAT IT DOES NOT DO: it draws the SAME character again, from that member's own stored look. If the user wants a CHANGED character - smaller, older, a different colour, a different thing entirely ('make the husband a white strawberry') - that is describe_cast_member, not this tool. Do not re-roll and hope, and NEVER re-draft the whole cast to change one member. Renaming a member, adding your own, and adding one from a photo are still webapp-only; say so if asked. COST: one standard image generation. It is charged at the model you pass in image_model (or the platform default portrait model if you pass none) - NOT necessarily at the rate the cast draft published, because the library does not record which model drew a face. Pass estimate_only: true for the exact number without spending, and state it before you ask for the go. THE GO THIS ONE NEEDS: one redraw, one named member, one priced ask. A complaint about a face ('the husband looks wrong') is a reason to OFFER the redraw with its price, never a go to buy it, and a bare 'yes' counts only when your priced ask for THAT member's redraw was the message immediately before it, nothing else was raised in between, and nothing the user asked for earlier is still outstanding. Never redraw more members than the user named, and never read a go for one face as a go for the rest of the roster. SPEND ETIQUETTE (the money grammar): in the webapp the priced button is the user's own finger; in chat YOUR tool call is not - so state the price IN THE SAME MESSAGE as the ask, and the user's explicit go is the button press. Never charge on inference: quoting is not asking, and after a price you wait for the yes. THIS APPLIES TO EVERY TOOL CARRYING THIS NOTE, including this one. A GO IS SCOPED TO ONE PURCHASE, AND IT MUST BE UNAMBIGUOUS. The user's instruction has to NAME the thing you are about to buy, or refer to it so plainly that it cannot mean anything else. A BARE AFFIRMATION - 'go', 'yes', 'ok', 'do it', 'just do it', 'sure' - counts ONLY when ALL THREE of these hold: the message immediately before it was YOUR priced ask for THAT EXACT action, nothing else was raised in between, and NOTHING THE USER ASKED FOR EARLIER IS STILL OUTSTANDING. That last one is the trap the others miss: if the user's OWN previous turn asked for something else - a refusal, a different scene, an edit, a redraw, a question - their 'just do it' may be answering THAT, and it is AMBIGUOUS even when your priced ask happens to be the last thing said in the thread. An ambiguous affirmation is not a go: ask WHICH one they mean and state that price again. WHEN IN DOUBT ABOUT WHAT A 'GO' REFERS TO, ASK. A wrong guess spends the user's money on something they never asked for, and nothing on this surface can undo it or give it back - asking costs one sentence. An episode's STAGES - cast portraits, episode create, fire, render - are each their own priced ask. A STANDING GO IS NOT UNLIMITED: 'just make it' or 'go ahead with the whole episode' authorizes the stages you PRICED IN THAT SAME MESSAGE, in the order you named them, and nothing beyond them - so do not re-ask per stage while it holds, and do not stretch it over a stage whose price the user never saw. IT EXPIRES THE MOMENT THE USER RAISES ANYTHING ELSE - a change, a question, a refusal, a redraw, a new idea - and after that the next stage needs its own priced ask. ONE STAGE IS NEVER COVERED BY A STANDING GO AT ALL: the FIRE (fire_story_video) is irreversible and the biggest single charge in the episode, so it always takes a go that NAMES firing, whatever was said earlier - see that tool's own note. A REDRAW IS NOT A STAGE: regenerate_story_frame and regenerate_cast_portrait are extra spends the user asks for one at a time, so state that price every time, even under a standing go. A standing go never carries to a different episode, and never to generate_video, generate_image or generate_audio - each of those is its own ask. ACCOUNT FOR YOUR OWN CALLS: if the user says something happened that you did not intend - a charge they did not expect, a step they did not ask for - RE-READ YOUR OWN TOOL CALLS IN THIS CONVERSATION before you answer, and tell them plainly which tools you called and when. NEVER SPECULATE ABOUT A CAUSE YOU CANNOT OBSERVE: not a button on an aicut card, not the user's own click, not their client. The aicut cards CANNOT SPEND - the only tools they ever call are the reads (get_video / get_image / get_audio), and their buttons either save a file or send a VISIBLE user turn into the chat - none of them calls a spending tool - so saying a card might have generated or charged something is false, not a hedge. (If a spend followed one of those visible turns, it was still YOUR call, and the honest answer names it.) If your call history disagrees with what you told the user, say what you actually called and let them correct you; do not invent an explanation that makes the two agree. IDEMPOTENCY: idempotency_key is optional and makes a retry safe. Set it on the FIRST call, not only on a retry - the job is addressed by the key, so a key added afterwards cannot find a job that was created without one. Reusing a key REPLAYS the job that key already created and returns it unchanged - even if you send a different prompt or different settings, and even after that job has finished. A key is therefore spent permanently. Do NOT reuse one to make another generation: two deliberate generations are two jobs and need two different keys (or none). ONE EXCEPTION, on render_story_video: replaying a key whose render FAILED answers 409 render_failed rather than replaying the failure, because a spent key stays spent - retry that one with a NEW key or with none. A KEY IS NOT SCOPED TO A TOOL: it addresses a job on the whole account, so reusing the key you gave generate_video on generate_story_video replays that first video instead of starting an episode. One key, one thing you made. (render_story_video is the one door that namespaces its own, which is why an episode's key can be reused on its render without colliding - but there is no reason to reuse it there either.) Never derive the key from the request body. You do NOT need to pass one to be safe against a duplicated delivery: aicut already derives a per-call key server-side, so a retry the transport makes on its own replays rather than charging twice. Pass your own only when YOU want to retry a call whose answer you never saw. OUTPUT: this returns JSON for you to read. When you report back to the user, give them the media URL plus a one-line summary. Do not paste the raw JSON, job ids, or internal field names into the conversation.