reloadium.com
Paste a topic, URL, or PDF/TXT/MD — get a multi-episode AI podcast with audio, transcripts, timelines and quizzes. 60+ languages.
First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com
Answer 67 · Act 127 · Transact 10 · Score: Not yet scored
Tool inspector
generateCarousel
Generate a multi-slide image carousel — a consistently-styled set of illustrated slides, each with a headline/body/label overlaid on an AI-generated background — and show it in chat both as a flip-through PDF (page 1 = slide 1, etc.) for reviewing/sharing the whole set as one file, AND as individually downloadable PNGs per slide, since a PDF alone can't actually be posted anywhere a carousel is meant to go (Instagram, LinkedIn, etc. only accept image files). Use this for an Instagram/LinkedIn-carousel-style visual explainer: a listicle, a step-by-step breakdown, a 'top N' post, a short educational sequence — anything that reads as a short series of visually cohesive slides rather than one image or a wall of text. Every slide shares ONE consistent illustration style — the first slide's background is generated fresh from `style` + that slide's own `imagePrompt`, and every later slide reuses the FIRST slide's actual image as a style reference (not just re-describing the style in words again) so the whole deck visually coheres the way a real illustrated series would, instead of drifting slide to slide. Keep `imagePrompt` about the SCENE/SUBJECT only (e.g. 'a lone hiker reaching a mountain summit at sunrise') — the shared `style` covers the artistic treatment (e.g. 'flat minimalist illustration, warm pastel gradient, soft rounded shapes'), so don't repeat style words in every slide's imagePrompt. `headline`/`body`/`label` are rendered as real, sharp overlay text — never described to the image model — so they're always exactly what you wrote, correctly spelled, however long or number-heavy they are; this deliberately avoids asking an image model to render the actual words, since image models are still unreliable at exact, legible multi-word text, and a wrong digit or misspelling baked into pixels is far harder to catch than a bad tool argument. Never ask the background image itself to include text/lettering. Pass `format` to match where this is going: '4:5' for an Instag…
Page: /
Input schema
| Property | Type | Required | Description |
|---|---|---|---|
slides |
array | yes | 1-8 slides, in display order. A single slide is fine for a one-image post. |
style |
string | no | Shared artistic style/treatment applied to every slide's background, e.g. 'flat minimalist illustration, warm pastel palette, soft gradients'. Defaults to a plain clean-illustration style if omitted. |
font |
string | no | Type style for the on-slide text — ALWAYS choose one to fit the brief's tone: 'serif' for luxury / elegant / premium / editorial / wedding / beauty / heritage; 'condensed' (tall uppercase headlines) for sales / sport / fitness / events / bold poster looks; 'handwritten' for casual / personal / friendly / kids / lifestyle; 'sans' only for neutral, technical or corporate topics. The card has a font picker, so the user can also switch it afterwards for free. |
format |
string | no | The shape the user asked for (9:16 for Reels/Stories/TikTok/Shorts) — it decides which tab the result opens on; the user can switch tabs afterwards. Defaults to '4:5'. |
Raw JSON schema
{
"type": "object",
"properties": {
"slides": {
"type": "array",
"description": "1-8 slides, in display order. A single slide is fine for a one-image post.",
"items": {
"type": "object",
"properties": {
"headline": {
"type": "string",
"description": "The slide's main on-screen text — short and punchy."
},
"body": {
"type": "string",
"description": "Optional smaller supporting text below the headline."
},
"label": {
"type": "string",
"description": "Optional small uppercase tag above the headline, e.g. 'STEP 1' or 'MYTH'."
},
"imagePrompt": {
"type": "string",
"description": "The background illustration's subject/scene only — style comes from the shared `style` param, don't repeat it here. Not needed when `imageUrl` is given."
},
"imageUrl": {
"type": "string",
"description": "Optional: use this photo as the slide's picture instead of generating an illustration — a product image from getShopifyProduct: pass its short `ref` (photo_1, photo_2, …), NOT the long URL (long URLs get corrupted when copied; a wrong character means a 404) — or a `url` from getBestImage, OR an image id (img_N) of one you generated/edited earlier in this conversation (editImage/generateImage; ids from findGeneratedImages). The photo is shown whole (not cropped) with the text beside/below it. Use different photos on different slides, and pick real photographs — skip logos, icons, maps, flags and tiny thumbnails. If you ALSO give imagePrompt, the photo is RE-STAGED by AI instead (so for photos the user wants unedited — 'no AI', 'as is' — give NO imagePrompt): the product is kept as it is and placed in the scene the prompt describes (billed image generation; can subtly alter small details like logos or text). To make real photos 'cooler', PREFER this (imageUrl + imagePrompt on each slide, one call, all slides in parallel) over calling editImage on each photo first — editImage runs one at a time, roughly 30s each. The imagePrompt describes only the SCENE around what the photo already shows — never add a product, tool or part the photo doesn't contain (do NOT ask for a knife in a photo of its pouch: the image model invents a wrong one). Keep the framing of the photo in imagePrompt: for a close-up or detail photo ask for a close-up in a new setting (macro, dramatic lighting), NOT for the whole product — the model invents whatever it can't see. Every re-staged slide is automatically checked against the original photo by a vision model and regenerated (up to 3 attempts) if the product was changed or the scene is poor; the result's `restageChecks` and summary say how each went — report any slide that used the original photo or only partly matched, don't hide it."
},
"restageCloseUp": {
"type": "boolean",
"description": "Set true ONLY when the user explicitly asks for AI on a close-up / detail photo (a macro, engraving, texture). By default such photos are kept as the real photo even when you give an imagePrompt, because re-staging a detail shot tends to invent or distort the product."
}
},
"required": [
"headline"
]
}
},
"style": {
"type": "string",
"description": "Shared artistic style/treatment applied to every slide's background, e.g. 'flat minimalist illustration, warm pastel palette, soft gradients'. Defaults to a plain clean-illustration style if omitted."
},
"font": {
"type": "string",
"enum": [
"sans",
"serif",
"condensed",
"handwritten"
],
"description": "Type style for the on-slide text — ALWAYS choose one to fit the brief's tone: 'serif' for luxury / elegant / premium / editorial / wedding / beauty / heritage; 'condensed' (tall uppercase headlines) for sales / sport / fitness / events / bold poster looks; 'handwritten' for casual / personal / friendly / kids / lifestyle; 'sans' only for neutral, technical or corporate topics. The card has a font picker, so the user can also switch it afterwards for free."
},
"format": {
"type": "string",
"enum": [
"4:5",
"9:16",
"1:1",
"16:9"
],
"description": "The shape the user asked for (9:16 for Reels/Stories/TikTok/Shorts) — it decides which tab the result opens on; the user can switch tabs afterwards. Defaults to '4:5'."
}
},
"required": [
"slides"
]
}
Similar websites
api.lmm.best
Connect AI models, tools and applications with LMM Forge. Explore model access, developer guides and open-source collaboration.
deskintab.dgkhan08.workers.dev
An operating system in your browser, where you and your AI agent share apps, files, and projects through WebMCP.
webmcp.agentsdesk.dev
Meridian Ops
cesium-browser-agent.pages.dev
Cesium Agent Lab