Gamma

Starts an AI edit of an existing Gamma presentation or document from a natural-language instruction. Use this when the user wants to change the content of a Gamma they already have — rewording, restructuring, adding or removing content — rather than creating a new one (use generate for that). If the user asks to edit the Gamma they just generated, pass the generationId from the previous generate call. Requires the Gamma file ID or URL and a prompt describing the edit. The edit is asynchronous: this returns immediately with an editId and status "pending". Poll get_edit_status with the editId, waiting a few seconds between checks (do not tight-loop), until the status is "completed" or "failed". On completion, share the summary of changes and the gammaUrl; on failure, report the error or reason. Do NOT call edit_gamma again to check progress (that starts a brand-new edit). Edits can add, remove, reorder and rewrite cards (slides) within a page; this tool cannot add new pages to a multi-page Gamma. Only one edit can run per Gamma at a time: wait for the current edit to complete or fail before starting another.

edit_gamma

Starts exporting an existing Gamma presentation or document to a downloadable file. Use this when the user wants a PDF, PowerPoint (pptx), or PNG image export of a Gamma they already have. Requires the Gamma file ID or URL and the format: "pdf", "pptx", or "png" (png returns a ZIP archive with one PNG per card). This returns an exportId immediately. Where an interactive widget is displayed, it shows export progress and the download link on its own, so do not call get_export_status. Where there is no interactive widget, such as a CLI or terminal client that does not render MCP Apps, poll get_export_status with the exportId, waiting a few seconds between checks (do not tight-loop), until the status is "completed" or "failed". On completion, share the download URL; on failure, report the error or reason. Do NOT call export_gamma again to check progress (that starts a brand-new export). The download link expires after about one week and is not tied to the API key, so share it carefully and download promptly.

export_gamma

Use this when the user wants to create a NEW presentation, document, webpage, or social media post, including turning a report, document or notes they supplied into slides or a summary deck. Use generate for any creation request unless the user references a template they want to create from. This tool can only create new content — to edit, modify, or refine an existing Gamma (including one it previously generated), use the edit_gamma tool instead. Gamma writes and designs the content itself; tell it what the user wants rather than pre-designing it. Only include optional parameters when the user explicitly requests or clearly implies them. Gamma has intelligent defaults. When in doubt, omit. When uncertain about user preferences, ask rather than assume. Always share the output gammaUrl with the user when it's available.

generate

Generates one standalone image from a text prompt. Use this when the user wants an image, illustration, or photo on its own — NOT a presentation, document, or webpage (use generate for those), and NOT a file export of an existing Gamma (use export_gamma). Choose a type ("illustration", "scene", "photo", "abstract") and sizePreset for aspect ratio; for brand styling, find a themeId with get_themes, or omit it for the workspace default. Generation is asynchronous (it takes longer than a request can stay open): this returns immediately with an imageGenerationId and status "pending". If your host displays the image widget, it shows generation progress and the finished image on its own — do nothing else. If you do NOT have a widget UI (for example a CLI or terminal client), poll get_image_generation_status with that id, waiting a few seconds between checks (do not tight-loop), until status is "completed" (then share the returned image URL) or "failed" (then report the error). Do NOT call generate_image again to check progress (that starts a new, separately billed generation).

generate_image

Use this when the user wants to create a NEW gamma by adapting, remixing, or transforming an existing template gamma. The new gamma starts from the source template gamma’s look and structure, and Gamma can adapt its cards and layouts to the new content; tell it what the user wants, including how long the result should be, rather than picking cards or pre-designing the deck. The prompt can direct changes — e.g. adding/removing/reordering cards, adapting for a different audience, transforming the subject matter, replacing images, populating cards from supplied data, or substituting variables and placeholders. Unlike the generate tool (which determines structure from scratch), this tool starts from an existing template gamma and uses it as the source material for the new one. Choose this tool whenever the user references an existing template gamma as the starting point — whether they want to populate it with new content, adapt it for a different audience or topic, generate a variation, or maintain consistent styling across multiple generated gammas. Requires a gammaId identifying the source template gamma in the user’s workspace. Important: the input gammaId MUST point to a template gamma; a regular non-template gamma won't be accepted. Prefer IDs returned by get_gammas with type="template" or the workspaceTemplates list from search_templates — never a search_templates exploreTemplates id, which this tool rejects. If the user provided a template ID, you may use it as-is. Do not pass URLs, placeholder IDs, or regular/non-template gamma IDs. If this tool reports that the gamma is not accessible or is not a template, recover by calling get_gammas with type="template" or search_templates (workspaceTemplates hits only) to find a valid template, or use generate if the user actually wanted to create from non-template source material. This tool can only create new content — to edit, modify, or refine an existing Gamma (including one it previously generated), use the edit_gamma tool instead. Only include optional parameters when the user explicitly requests or clearly implies them. Gamma has intelligent defaults. When in doubt, omit. When uncertain about user preferences, ask rather than assume. Always share the output gammaUrl with the user when it's available.

generate_from_template

Use this for one-shot creation of a MULTI-PAGE Gamma: a single Gamma containing several distinct pages under one URL. Ideal for sales rooms, proposal sites, onboarding portals, and microsites assembled from multiple sections (e.g. one page per prospect topic). Provide pages[] in the order they should appear; each page carries its own inputText and per-page settings (title, numCards, format, textMode, cardSplit, textOptions, imageOptions, path). File-wide settings (theme, folders, card dimensions, sharing, export, publish, overall title) apply to all pages. Prefer the generate tool when the user wants a single presentation, document, webpage, or social post; use this only when the user wants several distinct pages within one Gamma. This tool can only create new content — to edit, modify, or refine an existing Gamma (including one it previously generated), use the edit_gamma tool instead. Only include optional parameters when the user explicitly requests or clearly implies them. Gamma has intelligent defaults. When in doubt, omit. When uncertain about user preferences, ask rather than assume. Always share the output gammaUrl with the user when it's available.

generate_multi_page_gamma

Checks the status of an edit previously started with edit_gamma, using its editId. Poll this tool with the editId until the status is "completed" or "failed". If the status is "pending", wait a few seconds before checking again; do not tight-loop. Returns "completed" with a summary of the changes, "failed" with an error or reason, or "pending" if the edit is still running. On completion, share the summary and the gammaUrl; on failure, report the error or reason. Do NOT call edit_gamma again to check on an existing edit; that starts a brand-new edit.

get_edit_status

Checks the status of an export previously started with export_gamma, using its exportId. Where an interactive widget is displayed, the widget polls for completion and shows the download link automatically, so only use this tool if the user explicitly asks for status. Where there is no interactive widget, such as a CLI or terminal client that does not render MCP Apps, poll this tool with the exportId until the status is "completed" or "failed". If the status is "pending", wait a few seconds before checking again; do not tight-loop. Returns "completed" with a download URL, "failed" with an error or reason, or "pending" if it is still rendering. On completion, share the download URL; on failure, report the error or reason. The download URL expires after about one week and is not tied to the API key, so share it carefully and download promptly.

get_export_status

Use this when the user wants to browse available Gamma folders or search for a specific folder by name.

get_folders

Lists comment threads on an existing Gamma presentation or document, including their replies. Use this when the user wants to read, review, or summarize the comments or feedback on a Gamma. Requires the Gamma file ID or URL. Results are paginated, oldest activity first; use `after` with the `nextCursor` from a previous response to fetch the next page. Use `updatedSince` (ISO-8601 timestamp) to fetch only threads with activity after a given time.

get_gamma_comments