Supademo

Copy steps. Two modes: - **Within same demo** (sourceDemoId = targetDemoId): stepIds required — duplicates specific steps. New steps are appended at the end. - **Across demos** (different IDs): always copies ALL steps from source to target. stepIds is ignored because importStepsService does not support partial import.

copy_steps

Create a new unpublished Demo Agent draft using the same defaults, entitlement checks, voice, and intro screen as the interactive app. Use this once the user has described the agent's purpose clearly. It does not publish the agent.

create_agent

Create draft quick links with new, case-insensitive labels. An existing or repeated label fails with QUICK_LINK_LABEL_EXISTS; no existing link is overwritten. URLs must use HTTP, HTTPS, or email. Maximum 20 total quick links. The batch is atomic; this does not index knowledge or publish the agent.

create_agent_quick_links

Create a Monitor automation trigger. Conditions support intent, engagement, meeting booked (yes or no), and visitor profile fields; actions can email current workspace members or send to a connected HubSpot, Salesforce, Slack, Zapier, Marketo, or Webhook integration; Webhook actions require the Scale plan. Internal condition/action IDs are optional and generated automatically.

create_agent_trigger

Create a new Supademo demo from uploaded media handles — provided as attachments in the conversation or returned by get_upload_job. Each media item becomes one regular step in the same order as provided. Use this when a user has screenshots and/or videos and wants a new demo. If the conversation already contains uploaded media handles (for example as chat attachments), use them directly. Otherwise, for local files, first call create_upload_job, send the user the uploadUrl, then call get_upload_job after they finish. Pass images with their Image URL, width, and height; pass videos with their videoId. Supported media: - Image: provide { type: "image", imageUrl, width, height, text? }. Image URLs must be Supademo CDN URLs from a conversation attachment or the upload portal, and dimensions are required. - Video: provide { type: "video", videoId, text? }. The videoId must reference a completed video visible in this workspace. Do not ask the user for a domain URL. The backend derives the demo domain URL from the workspace. Folder behavior: - Omit folderId to create the demo in the shared workspace area (shared=true). - Provide folderId only when the user picks a folder. Use list_folders with type "Demo" to find folder IDs.

create_demo_from_uploaded_media

Create an empty Demo Hub using the same defaults as the interactive app: three starter categories ("Category 1-3"), a "Help" footer with Knowledge Base / Contact Support placeholder links, and workspace or white-label branding for the header logo and color.

create_demo_hub

Create Demo Hub categories (maximum 5 per hub). Optional order inserts at that position, shifting later categories. Creates apply in order and are not atomic; earlier successful operations remain if a later one fails.

create_demo_hub_categories

Create a Demo Hub from an existing showcase. This mirrors the UI action "Create Demo Hub from Showcase": it creates a Widget/Demo Hub, maps showcase sections to Demo Hub categories, and includes demo-backed showcase items. It does not use Route, RouteVersion, or isRouteHub. Every showcase section becomes a category, so a hub created from a showcase with more than 5 sections will exceed the 5-category limit that create_demo_hub_categories enforces when adding new categories.

create_demo_hub_from_showcase

Create trackable links for a demo in one batch. Optional variables personalize matching {{variable}} placeholders; optional expiresAt is an ISO timestamp. Requires trackable-link plan access and access to the demo. Creates links without changing existing links; returned URLs can expose published demo content. Returns one link for a single-item batch, otherwise an array.

create_demo_links

Create a new folder. Set personal=true for personal folder, personal=false for shared. Use parentId to create a nested subfolder. Type may be Demo, Showcase, or Video (default: Demo).

create_folder

Create one or more hotspots on steps. Position is specified as x,y percentage coordinates (0-100) relative to the step image. Styles: Circle, Tooltip, Area, Anchor, Pointer, Modal Animations: Ripple, Spinner, Pulse, Ping Width: Small, Medium, Large Tooltip positions: bottom, top, left, right, autostart Border radius: Square, Sharp, Soft, Round, Pill, Roundest Text align: Left, Center, Right

create_hotspots

Create a showcase using the same core defaults as the interactive app: published, one starter section, workspace CTA/branding defaults, and optional Showcase folder placement.

create_showcase

Create personalized/trackable showcase sharing links. Variables are string values: name, email, and company are default UI variables; custom keys must match existing {{variable}} placeholders to render. Returns the created IDs and URLs. Requires Scale+ trackable-link access.

create_showcase_links

Create sections in a showcase. Omit name to use the existing default. Batch creates apply sequentially and are not atomic.

create_showcase_sections

Create a new demo step from an existing media library item returned by list_media_library_items. Images become regular image steps with a default hotspot. Videos duplicate the selected completed VideoProject and attach the duplicate to the new step, so the original media library item remains reusable. This does not upload files. If the conversation already contains uploaded media handles (for example as chat attachments), use those directly with create_demo_from_uploaded_media, create_steps, or replace_step_media. Otherwise, if the user has a local file, first call create_upload_job and send them the returned uploadUrl; when they say they're done, call get_upload_job, then use those tools with the returned handles.

create_step_from_media_library_item

Create one or more steps. Each step must be one of three explicit types: image, video, or chapter. If the conversation already contains uploaded media handles (for example as chat attachments), use them directly. Otherwise, for local files, first call create_upload_job, send the user the uploadUrl, then call get_upload_job after they finish uploading. **Image step:** provide { type: "image", imageUrl, width, height, text? }. A default hotspot is added, matching the app's current image-step behavior. **Video step:** provide { type: "video", videoId, text? }. The videoId must reference a completed video visible in this workspace; the backend duplicates it before attaching it to the step. **Chapter step:** provide { type: "chapter", chapterType, chapter? }. The tool creates the step, chapter, and any inline buttons/formFields you specify. Use position to insert at a specific 1-based step number — existing steps are shifted down. Omit position to append at the end. When multiple items include position in one call, they are processed in array order against the evolving step list. **IMPORTANT:** For chapter steps, omit theme, layout, colors, skip, enabled, and button styling fields unless the user explicitly specifies them. When omitted, the backend automatically applies the workspace's default chapter template. Only pass fields the user explicitly requests — do not infer or copy values from other chapters.

create_steps

Create workspace tags with name (1–50 characters) and optional hex color (default indigo). Names are unique per workspace, case-insensitively; an existing name fails with TAG_NAME_EXISTS. This does not attach tags to assets. Processed sequentially; earlier creations can persist if a later item fails. Returns one tag for a single-item batch, otherwise an array.

create_tags

Create a short-lived upload job and get a link the user opens in their browser to upload local files (images, videos, PDFs) into this workspace. Use this only when the user has local files, the conversation does not already contain uploaded media handles (an Image URL with width/height, a videoId, or a PDF URL), and the user cannot attach files directly in this interface. If the interface supports message attachments (e.g. Supademo AI Command), ask the user to attach the files to their message instead. If handles are already present — for example as chat attachments — use them directly with create_demo_from_uploaded_media, create_steps, or replace_step_media. Flow: call this tool → give the user the uploadUrl → they upload there while logged in to the same Supademo account; the portal uploads into this job's workspace automatically → when they say they're done, call get_upload_job with the jobId to fetch the resulting identifiers. The job expires 60 minutes after creation.

create_upload_job

Start an AI edit of a video project, in place, from its original recording. Supademo watches the recording, works out its objective and the steps taken to reach it, and edits the project towards that. What the edit makes depends on where the video lives. Today only the video of a demo step is supported: it becomes a click-through demo with a pause hotspot on every step, dead time cut, and typing, scrolling and loading sped up. Other videos fail with VIDEO_EDIT_UNSUPPORTED. Take videoProjectId from the step in get_demo. AI video edit is in beta and can get things wrong. Before calling, tell the user it is a beta feature, and that the edit replaces the project's existing cuts, speed changes and hotspots, removes its zooms, spotlights and camera resizes, mutes the recording's audio, and invalidates any export. The video keeps its title, and the demo's title and description are left as they are. The edit overwrites the project when it finishes, including any other edit made in the meantime. Until then the demo shows the unedited recording: when you have just created the demo from it, say that what is there now is the raw upload, which the edit will rework. Returns at once with the run's id and status; poll get_video_ai_edit with the id. For 10 minutes after starting an edit, calling again returns that run with its current status (which may already be completed) instead of starting another.

create_video_ai_edit

Permanently delete an agent, every draft and published version, its intro screens, monitor data, evaluation criteria, and triggers. Reusable knowledge remains in the workspace; unreferenced demo/video sources and their vectors are cleaned up.

delete_agent

Soft-delete one Monitor trigger and disable it immediately. Delivery history is preserved.

delete_agent_trigger

Delete one or more chapters from steps. This deletes each chapter and all its buttons and form fields.

delete_chapters

Permanently delete a Demo Hub with all its categories and content links (the underlying demos/showcases are not touched). Any site embedding this hub will stop showing it.

delete_demo_hub

Delete Demo Hub categories and their content links without deleting underlying demos/showcases. This immediately changes embedding sites. Deletions apply in order and are not atomic.

delete_demo_hub_categories

Delete trackable demo links by linkId, including their personalization values. Existing shared URLs stop working; the underlying demo is preserved. Requires access to the demo. Processed sequentially; earlier deletions can persist if a later item fails. Returns one deletion result for a single-item batch, otherwise an array.

delete_demo_links

Delete an entire target-language translation from a demo, including its translated text and media rows.

delete_demo_translation

Delete a Demo, Showcase, or Video folder, including subfolders. Demos inside are archived (not permanently deleted); showcases inside are moved to the root; non-step videos in Video folders are permanently deleted (step-attached videos are unlinked only).

delete_folder

Delete one or more hotspots from steps.

delete_hotspots

Permanently delete a showcase. This matches the Showcase model behavior; unlike demo folders, showcases do not have an archived state.

delete_showcase

Delete personalized/trackable showcase links by linkId, invalidating their sharing URLs. Deletions apply sequentially and are not atomic. Requires Scale+ trackable-link access.

delete_showcase_links

Delete showcase sections and all their content links; underlying demos and videos are preserved. Batch deletions apply sequentially and are not atomic.

delete_showcase_sections

Delete one or more steps from a demo. Remaining steps are automatically renumbered.

delete_steps

Delete workspace tags by tagId and detach them from every demo/showcase using them. Underlying demos/showcases are preserved. Include all affected assets in the authorized scope before deleting a shared tag. Processed sequentially; earlier deletions can persist if a later item fails. Returns one deletion result for a single-item batch, otherwise an array.

delete_tags

Remove voiceover audio from specific steps or entire demo. Pass stepIds to delete from those steps, or omit to delete ALL voiceovers in the demo.

delete_voiceover

Discover public page URLs before adding a multi-page website as agent knowledge. Use returned links with add_agent_website_knowledge full mode. Returns at most 300 links; totalDiscovered and truncated report when the site has more.

discover_agent_website_pages

Create a new unpublished agent by copying the source agent's draft settings and knowledge attachments. Intro screen, evaluation criteria, triggers, sessions, and checklist results are not copied.

duplicate_agent

Duplicate a demo with all its content (steps, hotspots, chapters, video projects, HTML edits, translations). Creates a copy titled 'Original Title(Copy)'.

duplicate_demo

Create a brand-new demo from a specific published version of an existing demo. The copy is fully independent (all content ids are remapped) and receives its own version 1 when publishing is unrestricted for the workspace; otherwise it remains a draft. The copy remains private until its visibility is changed with update_demo_settings. The source demo is not modified.

duplicate_demo_from_version

Duplicate a Demo Hub including all settings, categories, and content references. The copy is named "<original> (copy)".

duplicate_demo_hub

Duplicate a showcase, including sections, resource-center content references, workspace content source metadata, and tags. Legacy demo-only sections are copied as modern demo SectionContent rows.

duplicate_showcase