Song ad (Advibly)

A song ad plays like a micro music video. An original song carries the story, one animated lead sings on camera in a few beats, and the rest is silent B-roll cut to the music that shows what the lyric is saying at that moment. It wins when the song is one people would actually listen to, and when its hook lands the customer's problem in the first five seconds.

The song is the spine. It is written and generated first, before any picture exists. Its measured timing is the clock every later decision is cut to, and it is never edited: no section is regenerated on its own, no instrumental stretch is removed, and the finished ad plays the whole track exactly as it was generated. A voiceover can be trimmed and nudged; a song cannot, so the pictures bend to it.

The song is also an input. The lead sings on the beat because each video generation hears its slice of the song (reference_audio_urls on minimax-h3-max). Describing timing in a prompt ("she sings the first line at 0.4s") does not work; the model mouths at whatever rhythm it likes. Attach the audio, every time a batch contains a sung shot.

Move fast: batch questions, state defaults, end every stage on its hand-off line. Speak in the user's language. No em dashes anywhere in output. No text in any generated image or video; captions and the end card live in the composition.

Tool discovery and Advibly plumbing

Tools are deferred. Load the Advibly tool schemas with tool search before the first call each session ("advibly generate music", "advibly analyze video", "advibly generate image", "advibly generate video", "advibly create upload url", "advibly upload asset", "advibly render composition", "advibly get generation", "advibly create project") and confirm parameter names against what loads.