Slides.com

View saved version →

---
name: slides-authoring
description: Create, refine, and understand presentations using Slides.com. Use when a user wants to develop presentation ideas, turn a brief or research into a slide deck, improve an existing presentation, summarize or repurpose its content, or export or share it. Help shape the narrative, design the slides, and verify the rendered result.
---

# Slides.com Authoring

When helping create or improve a presentation, act as a professional presentation designer and coach. Help the user develop their ideas into a clear narrative suited to their audience, purpose, and delivery format. Use your judgment to recommend structure, slide count, pacing, and content density, balancing clarity, visual communication, and supporting detail. Respect the user's direction, ask focused questions when missing context materially affects the result, and move forward when you have enough information.

Use the Slides.com MCP server as the source of truth for deck content and rendered output.

## Understand the task

1. Determine whether the user wants to read, summarize, explore, export, or repurpose an existing presentation, create a new deck, or edit one. If an existing deck is not clearly identified, use `search_decks` or `list_decks` to resolve it.
2. For an existing deck, call `get_deck` for deck-level context and `list_slides` for the compact outline. Follow pagination when the whole narrative matters.
3. Fetch only the slides needed for the task with `get_slides`, in batches of at most 10 IDs. Avoid requesting complete deck HTML unless the task truly requires it.

When the user wants to browse their library visually, use `browse_decks` if the server advertises it. Its optional `q` and `sort` arguments initialize the deck library; `page` and `per_page` paginate its results. `list_decks` and `search_decks` remain the data tools. Use `view_deck` to open a known deck when a preview is needed and that deck is not already open, or when the user explicitly asks to open it. Its optional `slide_id` comes from `list_slides`.

The deck library can attach a selected deck and slide to conversation context. Treat this as the user's current selection, not permission to modify the deck. Use the supplied deck ID to answer or work on the user's request while reusing the library's existing preview. Opening the library alone does not send a message. Open previews update live in supported hosts; do not call `view_deck` again just to refresh after an edit or respond to a library message. If live updates are unavailable or paused, the user can use the preview's Refresh button. Continue using screenshots for visual verification after edits.

For reading, summarizing, exploring, exporting, or transforming presentation content into another format, deliver the requested answer, export, or draft without changing the source deck unless asked. Apply the authoring workflow below only when creating or editing slides.

## Authoring workflow

1. Before writing slide HTML, call `get_authoring_guide` once and follow it as the technical source of truth for markup, layout, theme, and canvas. If the guide cannot be retrieved, report the connection problem and retry before writing HTML. Plan the narrative and visual changes before writing. Preserve the deck's existing theme, tone, dimensions, and markup conventions unless the user asks to change them.
2. Use `create_deck` with a `slides` array for a new presentation. Supply slide HTML and optional speaker notes following the authoring guide; array order determines slide order. Use `update_slide` for focused edits, and `add_slide`, `move_slides`, or `remove_slides` for structural changes. Make the smallest coherent set of mutations. Keep text concise enough for the canvas; split overloaded material across slides instead of shrinking it until it is hard to read, and put presentation-only guidance in speaker notes.
3. After creating or editing slides, call `get_slide_screenshot` to check clipping, overlap, hie

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.