Skip the brief. The product page already says what the product does - start there.
Try it free →1 free video · no credit card
Every product page is a finished brief that nobody uses: it already carries the name, the positioning, the benefit copy someone argued over, and the objections the FAQ answers. Writing an ad script from scratch means re-deriving all of it from memory, usually less accurately. Reeloop reads the URL instead - Claude pulls the product context out of the page, writes a short-form script grounded in what is actually there, and the pipeline renders a scene per line with an AI voiceover and burned-in captions. For a store with two hundred SKUs this is the difference between video for the hero product and video for the catalogue.
A good product page supplies the concrete material a script needs: what the thing is, who it is for, the two or three benefits the brand has decided to lead with, and the specifics - material, size, compatibility - that make a claim credible rather than generic. That is most of a script. What a URL cannot supply is the angle. The page is written for someone already looking at it; an ad has to interrupt someone who is not. So treat the generated script as a grounded first draft and choose the angle yourself: problem-first for a product whose benefit needs setup, demonstration-first for something visual, comparison-first where the buyer is already choosing between options. A thin page produces a thin script, and the fix is upstream - if the page does not say what the product does, no generator will infer it. Pages behind a login, heavy client-side rendering, or an aggressive bot wall may not be readable at all, in which case pasting the description directly works exactly as well.
The reason this matters commercially is scale. One product with a hand-made video is normal; a catalogue where every SKU has video is rare, because the per-product cost of scripting, shooting and editing has always made it irrational below the top sellers. At 3 credits for a standard 30-second video the arithmetic changes: the long tail becomes affordable, and the products that never justified a shoot get the creative that lets them be advertised at all. Practical order of work: start with the SKUs that already convert, since a video that lifts an established seller pays for the batch; use one style across the catalogue so the set reads as one brand rather than two hundred experiments; and vary the hook per product rather than the format. The API and MCP server exist for exactly this - a store can wire generation into its own catalogue workflow instead of pasting URLs one at a time.
A script written from a page can only be as accurate as the page, and it can still go wrong in ways worth checking before anything ships: a spec read as a benefit, a limited-time price stated as permanent, a compatibility claim generalised past what the page says, or a comparative claim about a competitor that the page merely implied. Read every script against the product before you approve it - Reeloop holds the draft for review with the exact credit cost shown, precisely so this check happens before you spend rather than after you publish. Regulated categories deserve more care, not less: supplements, financial products, and anything making a health or earnings claim carry rules that apply to you as the advertiser no matter what produced the copy. The generator removes the typing, not the responsibility.
Paste the product page URL
Pick an angle and a style
Review the generated script against the product
Approve to render, then export for your ad platform
Any publicly reachable page. Pages behind a login, ones that render entirely client-side, or ones with an aggressive bot wall may not be readable - pasting the product description directly works just as well.
No. Claude uses the page as source material and writes a short-form script for speech, which is a different shape from page copy. Review it against the product before approving - you are responsible for the claims it makes.
Yes, and that is the point. Reeloop has a public API and MCP server, so generation can run from your own catalogue workflow rather than one paste at a time.
Related tools
No camera. No editing. Ready in minutes.
Start for free →1 free video · no credit card