Arcade

Use this when the user wants to enrich an existing Brand Kit with website pages, blog posts, help docs, or landing pages. Add a link source to an existing Brand Kit to enrich its branding data. Sources are processed asynchronously — the Brand Kit improves as each source is ingested. Pass URLs of websites, blog posts, help centers, or documentation pages. The system scrapes and analyzes them for brand colors, fonts, tone, and style. Provide URLs you own or are authorized to scrape. Arcade does not bypass robots.txt, authentication, or other access controls, and will not fetch content that violates the source site's terms of service.

add_brand_kit_source

Use this only when the user asks how many Arcade credits they have, or what a video would cost. Do not call it otherwise, and do not bring up credits or cost before creating a video unless the user asks. Returns the workspace's credit balance and, when a mode or length is given, the credits create_video would reserve for that video, using the same rules as the charge: the plan's length limit, the current prices, and, with no mode named, the model the user last picked in the app or High.

get_credits

Check an Arcade video generation. Each call waits up to 30s internally. A processing result requires another check; succeeded means the video can be edited through viewUrl, while MP4 export may still be pending. A failed result contains an error. Accepts the generationId returned by create_video or edit_video, or a raw promptVideoGenerationId from the Arcade editor. For an edit, succeeded means the new version is published and failed means the video is unchanged.

get_generation_status

Use this when the user wants to set up a new Brand Kit for a company or product from a website domain. Create a Brand Kit from a website domain. The Brand Kit extracts colors, logos, fonts, and style guidelines from the website. IMPORTANT — Before calling this tool, ask the user conversationally if they have any web pages that represent their brand well — things like blog posts, product pages, help docs, or landing pages. Do not present a numbered list or multiple-choice options. Just ask naturally in conversation. After the user responds: 1. Call this tool with the domain 2. Immediately add any URLs the user mentioned via add_brand_kit_source 3. Sources process in parallel with Brand Kit generation — do not wait between steps This tool returns immediately — the Brand Kit generates in the background (typically 2–4 minutes). Before calling create_video, use list_brand_kits to confirm the Brand Kit has status "ready".

create_brand_kit

Use this when the user asks to create, generate, or make a branded product video, demo video, or marketing video — Arcade produces the video with visuals, animations, and narration from a prompt, preset, screenshots, website URLs, or existing Arcade demos. Do not use to write a script, storyboard, or shot list — answer those conversationally. BEFORE CALLING: Check that the conversation or usable sources establish concrete subject matter. A topic or product name plus a `brandKitId` is not enough: ask one focused question for the intended angle and supporting content, for example "What should viewers understand about your product, and what facts or source material should I use?" A preset supplies story direction, not missing product facts. Reuse the whole conversation, supplied material, and settled creative choices to write a specific brief. Clarify only material gaps that would change the story or required media, together in one short exchange. The brief fields below are writing guidance; the user need not complete a questionnaire. Choose sensible creative defaults for execution details such as pacing and transitions. PREPARE THE PROMPT: These fields guide your writing, not an interview or required questionnaire. Write a self-contained creative brief from what is already known: topic and video type; audience; purpose and closing action; one core viewer takeaway; a beginning-to-end narrative in untimed prose; ranked must-include moments; supported facts; tone and visual direction; narration/no narration, original audio, and music treatment; asset roles and important constraints. Preserve the user's latest confirmed choices and distinguish them from suggestions the wizard may refine. Avoid unnecessary scene numbers or fixed timings; the wizard plans the execution. Keep the selected duration in `targetLength` rather than duplicating it in the brief. CREATIVE DIRECTION: Choose one audience-specific creative idea from the available context. Make the opening earn attention with a relevant question, recognizable tension, or visual reveal grounded in the subject. Build a story in which each beat advances the takeaway: establish something the audience cares about, make a supported idea tangible through a demonstrated moment, and deliver a payoff that resolves the opening before the closing action. Give the visuals a cohesive concept: describe a subject-specific motif, a clear focal point, and purposeful changes in scale, composition, or visual contrast across the story. Use motion to reveal, connect, or transform meaning; keep on-screen copy concise and readable. Make concrete directorial suggestions about what viewers see and why it matters, beyond style adjectives. These are creative suggestions the wizard may refine, not fixed scene timings or new product facts. Preserve confirmed story beats and their order, tone, media, and audio choices; strengthen execution within them. Choose any unsettled execution details directly without another creative-choice exchange. Put the creative idea and narrative near the start of the brief so they guide how the facts and assets become a video. GROUND CONTENT AND ASSETS: Carry concrete facts from source content you actually retrieved or were given, not guesses from a URL or product name. Preserve the supplied facts and their limits explicitly in the brief. Product claims include illustrated UI: instruct the wizard to show only supported fields and controls, without adding due dates, priorities, checklists, counters, offers, or website addresses unless supplied. Neutral example task names and owner labels may illustrate a supported capability; additional features are not decorative details. Do not invent metrics, testimonials, capabilities, or asset IDs. A style reference supplies style, not product facts. For each attached demo, image, or video, explain what it should show or inform and whether it is visible media, factual context, or a style reference. Prefer authentic product screenshots/recordings for demonstrations. Put already available content from private or inaccessible pages in the brief; do not rely on the wizard fetching them. Use `websiteUrls` only for reachable public source pages, and explain their roles in the brief. The wizard runs without follow-up questions, so resolve material uncertainty before calling. FORMAT AND MODE: Explicit choices win. Set `aspectRatio` to a ratio the user states, even when the platform suggests another. For Instagram Reels, TikTok or YouTube Shorts with no stated ratio, use 9:16. Otherwise omit it for a 16:9 video; ask about format only when an unclear placement would change it. Set `generationPreference` only when the user asks for Light, Medium or High mode; it applies to this video only. Otherwise omit it: Arcade uses the model the user last picked in the app's model menu, or High if they have not picked one since the AI credits launch. Never ask the user to choose a mode. Do not bring up credits or cost before creating a video; if the user asks, use `get_credits`. BRAND KIT: Every video uses a Brand Kit, so never offer to generate without one. Pass `brandKitId` only when the user named or chose a kit; a clear brand match in the request counts. Otherwise omit it: create_video uses the workspace default or the only ready Brand Kit and names it in its reply, or creates nothing and says what to ask the user. `list_brand_kits` marks a sample brand: a stand-in Arcade provides, not the user's own brand. If the only ready Brand Kit is a sample brand, ask the user whether to use the sample brand or create their own Brand Kit with `create_brand_kit` first. Provide either a `preset` (one of: product-release, explainer, sales, social-media — selected internally based on the user's intent, never surfaced by name) or a free-form `prompt`. Prompts can be up to 20,000 characters, and full detail is welcome when it helps make the video specific. Other optional inputs: `websiteUrls` (≤3), `flowIds`, `imageIds`, `videoIds`. Time estimate by length (share it once the length is known): ~1–2 min for 15s/30s/45s, ~2–3 min for 60s/90s/120s. ATTACHED AND REFERENCE MEDIA: When the user attaches screenshots or other images in this chat for the video, call `upload_image` with them before `create_video`, without asking first, then pass the returned IDs in `imageIds` and give each image a role in the brief. A public YouTube video can be a style reference: put its watch URL in `websiteUrls` or the prompt and say in the brief that it guides style only (pacing, palette, motion), never product facts. Arcade cannot receive private video files from chat; if the user offers one, say so briefly and continue without it. Reuse a stated duration as `targetLength` (15s/30s/45s/60s/90s/120s). If duration is a material unresolved choice, ask with the other necessary clarification, never in a separate length-only exchange. If the user delegated the choice or has no preference, use the applicable preset default or 30s. Do not re-ask a settled length. Starts generation and returns a `generationId`. Check completion with `get_generation_status`; each call waits up to 30s internally and may return `processing`, requiring another check. A `succeeded` result includes the edit link in `viewUrl`, even while MP4 export is pending. Share that link before starting `preview_video`, so the user can open the video during export. `preview_video` accepts the original `generationId` as `videoId` and waits for export to display the inline player. A `failed` result contains an error and no edit link; report that error instead of requesting a preview.

create_video

Use this when the user asks to change a video made in this chat with create_video or edit_video: new wording, pacing, a scene, colors, the format (for example 9:16 for TikTok), or going back to an earlier version. Arcade changes the same video, as one more message in its editor chat, and publishes a new version. Do not use it to make a different video; use create_video for that. Pass the latest `generationId` returned by create_video or edit_video for that video. Videos made elsewhere, such as in the Arcade editor, cannot be changed here; send the user the video's edit link instead. Write `change` as one self-contained instruction in the user's words, with any detail from the conversation it needs. The edit runs without follow-up questions. Do not bring up credits or cost before the edit; if the user asks, use `get_credits`. If the video is still being made or changed, wait for get_generation_status to finish before you call this tool. Returns a new `generationId` for the edit; use it, not the earlier one, from then on. Check completion with `get_generation_status`; succeeded means the new version is published and `viewUrl` opens it. Then call `preview_video` with that generationId to show the new version. A failed result means the video is unchanged; report the error.

edit_video

Use this when you need the full record of a specific Arcade demo by its id (typically following search). Fetch a single Arcade demo by id. Returns the demo title, a short descriptive text, a canonical URL, and metadata. Use the id returned by `search` or `list_demos`.

fetch

Use this when the user asks how a demo is performing across distribution channels or custom links. Get demo analytics broken down by custom link (attribution). Shows views, plays, completions, CTA clicks, and play time per distribution channel/custom link. Requires a Growth+ plan.

get_demo_attribution

Use this when the user asks which companies, accounts, or leads have engaged with their demos. Get companies that interacted with your demos, with firmographic data (industry, employee range, revenue) and engagement scores. Pass a flowId for per-demo companies or omit it for team-wide leads. Requires a Growth+ plan.

get_demo_companies

Use this when the user asks how a specific Arcade demo is performing — views, plays, completions, drop-off, or CTA clicks. Get performance analytics for a specific Arcade demo: views, plays, completions, CTA clicks, average play time, and step-by-step dropoff analysis. Requires teamId and flowId (use list_demos to find these). Requires a Growth+ plan. The result renders as an interactive widget. Do NOT list, enumerate, or summarize the metrics in your response — say "Here's the performance data" and let the widget speak for itself.

get_demo_performance