Havi Slides

Widget-only: apply a theme to a presentation.

apply_theme

Widget-only: fire-and-forget cancel of speculative pre-generation (GA-953).

cancel_pregen

Create a new presentation on any topic. Returns an interactive slide viewer. Only set optional parameters when the user explicitly mentions them. Omit everything the user does not specify. Args: topic: Subject matter for the presentation (required). When files are passed, this holds the user's own instructions for the deck (focus, audience, structure), not a summary of the files. num_slides: Number of slides. Only set if user states a number. language: Content language. Only set if user requests non-English. text_content: Text density. Allowed values ONLY: minimal, concise, detailed, extensive. tone: Presentation tone. Allowed values ONLY: professional, conversational, technical, academic, inspirational, humorous. audience: Target audience, e.g. business, high_schoolers, college_students, creatives, tech_enthusiasts, or custom text. image_style: Image style. Allowed values ONLY: illustration, photorealistic, abstract, three_d, line_art. image_keywords: Keywords guiding image selection. image_source: Image source. Allowed values ONLY: ai, search, pexels, unsplash. files: Pass the uploaded files (PDF, DOCX, PPTX, PNG, JPG) only when the user wants the presentation based on, converted from, summarised from or redesigned from them, or uses them as references. Leave empty when the request is about a topic the files do not cover or the user says to ignore them.

create_presentation

Edit a presentation using natural language instructions from the user WHEN TO USE: - User wants to MODIFY an existing presentation that was created in this conversation - Trigger phrases: "edit", "change", "update", "make it", "add", "remove", "move", "fix", "tweak", "adjust" - Examples: • "make slide 2 more concise" • "add a slide about pricing" • "change the theme to something darker" • "remove the last slide" • "add more visuals" • "i don't like this slide" (pass exactly as-is) DO NOT USE: - No presentation exists in this conversation → Ask user to create one first - User wants to create a NEW presentation → Use create_presentation - User wants to list/retrieve saved presentations → Not available here; tell the user only decks from this conversation can be edited - User wants to export → Tell the user to use the Export button on the deck card; if the card is gone, reopen it with open_presentation_editor - You don't have a valid presentation_id → Ask user to create or open a presentation CAPABILITIES: The backend agent can: ├─ Content: Modify text, add/remove bullet points, change titles, add speaker notes ├─ Slides: Add, remove, reorder, duplicate slides ├─ Images: Add, replace, remove images; change image style ├─ Theme: Change colors, fonts, overall visual style ├─ Layout: Adjust slide layouts, text positioning └─ Navigation: The agent auto-detects which slide user is viewing (no slide number needed) CONTEXT AWARENESS: - Agent tracks which slide user is currently viewing in the widget - Agent maintains conversation context for multi-turn edits - User can refine iteratively: "make it shorter" → "now add examples" → "perfect, do the same for slide 3" ⚠️ CRITICAL INSTRUCTION — PASS USER MESSAGES EXACTLY: ┌─────────────────────────────────────────────────────────────────────────────┐ │ Do NOT interpret, expand, rephrase, summarize, or rewrite the user's input. │ │ Pass the instruction parameter EXACTLY as the user typed it. │ │ The backend agent handles clarification — your job is only to pass through. │ └─────────────────────────────────────────────────────────────────────────────┘ Examples of correct pass-through: User: "i do not like this slide" → instruction: "i do not like this slide" User: "make it better" → instruction: "make it better" User: "more professional" → instruction: "more professional" User: "add something about our team" → instruction: "add something about our team" User: "idk fix it" → instruction: "idk fix it" ❌ WRONG — Do not do this: User: "make it better" → instruction: "Improve the slide by enhancing the content quality and visual design" ← NO! Args: presentation_id: UUID of presentation to edit (REQUIRED — from create_presentation response) instruction: User's EXACT message, word-for-word (REQUIRED — do NOT rewrite) conversation_id: Optional. Auto-tracked by widget for multi-turn context. files: Pass the uploaded files (PDF, DOCX, PPTX, PNG, JPG) only when the edit is based on them, for example "add a slide from this report" or "put this picture on slide 3". Leave empty otherwise. Keep instruction as the user's exact words. Returns: ToolResult with updated presentation widget RESPONSE GUIDANCE: Accompany the widget with a brief text response (1-2 lines max). STRUCTURE: 1. Confirm what was changed (1 line, specific) 2. Optionally prompt for next action or confirmation TONE: Brief, specific, conversational. Match the energy of the edit size. EXAMPLE RESPONSES: ✅ GOOD (small edit): User: "make the title shorter" Response: "Shortened the title. Anything else?" [Widget] ✅ GOOD (content change): User: "add a slide about pricing" Response: "Added a pricing slide after slide 4. Want me to adjust the details?" [Widget] ✅ GOOD (theme change): User: "change to a dark theme" Response: "Switched to a dark theme throughout. Let me know if you'd like to tweak the colors." [Widget] ✅ GOOD (vague request — agent asked clarification): User: "i don't like this slide" Agent response: "What would you like me to change — the content, layout, or visuals?" [Widget with agent's clarifying question] ✅ GOOD (multi-turn): User: "make it more concise" Response: "Condensed the text. Want me to do the same for other slides?" [Widget] ❌ BAD (too verbose): "I've successfully updated your presentation by shortening the title on slide 2. The new title is now more concise and impactful. You can continue editing, change the theme, export the presentation, or make additional modifications..." ❌ BAD (vague confirmation): "Done." [Widget] ❌ BAD (over-explaining what changed): "I modified the slide by adjusting the title length, reducing it from 12 words to 6 words, which improves readability and visual hierarchy..." EDGE CASES: 1. NO PRESENTATION EXISTS User: "edit slide 2" Response: "There's no presentation open yet. Want me to create one? Just tell me the topic." 2. PRESENTATION_ID NOT FOUND / INVALID Response: "I couldn't find that presentation. It may have been deleted or expired. Want to create a new one?" 3. EDIT FAILED (backend error) Response: "Couldn't apply that edit. Try rephrasing, or let me know what you'd like to change and I'll retry." 4. AMBIGUOUS MULTI-PRESENTATION CONTEXT (rare) User has multiple presentations discussed in conversation Response: "Which presentation — the [topic A] deck or the [topic B] one?" 5. USER ASKS TO EDIT SOMETHING OUTSIDE SCOPE User: "edit my Google Slides presentation" Response: "I can only edit presentations created here. Want me to create a new presentation on the same topic?"

edit_presentation

Widget-only: enhance an image generation prompt using slide context.

enhance_image_prompt

Widget-only: generate a smart diagram from slide content.

generate_diagram

Widget-only: generate or resolve a slide image.

generate_image

Widget-only: generate N candidate images for the MediaSidebar (non-streaming).

generate_image_candidates

Widget-only: generate intro-slide variations (blocking).

generate_intro_variations

Widget-only: generate and persist a presentation outline (blocking).

generate_outline