Skip to main content
Glama

Server Details

250+ finished slide layouts and 40+ themes your agent can search, fetch and build a deck from

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 22 tools

Disambiguation4/5

Most tools map to a distinct resource+action (template CRUD, object CRUD, theme/layout catalog reads, deck composition), and descriptions explicitly cross-reference the alternatives ('use this instead of update_template', 'use render_slide instead of get_layout when you know the text'). A few pairs remain genuinely close — check_slots vs render_slide, get_layout vs render_slide, check_deck vs check_slots, and export_pptx vs save_template vs suggest_deck all produce 'a deck' in different forms — but the descriptions resolve each with explicit routing guidance.

Naming Consistency5/5

Every name is snake_case with a leading verb (list_, get_, add_, update_, remove_, check_, publish_, save_, render_, export_, suggest_). Verb+noun pairs are predictable and pluralization of list_* resources is uniform.

Tool Count4/5

22 tools is on the heavy side, but the server genuinely spans several sub-domains: layout/theme catalog, rendering and validation, template lifecycle with drafts and publishing, per-slide object editing, media, and team review/feedback. Each tool covers a coherent slice, though a few (get_starter_kit, list_template_versions, list_pending_reviews) are narrow and push the set toward the upper bound.

Completeness4/5

Core lifecycle is well covered: find layouts/themes, validate, render, compose, save, update, publish, version, and export, plus per-slide object add/update/remove and read-only collaboration surfaces. The notable gaps are deliberate web-only actions — deleting templates/slides, approving or sending back reviews, restoring versions, uploading media — which agents can only route around by telling the user to act on the web.

Available Tools

22 tools
add_objectsAdd objectsAInspect

Add text boxes, shapes and images on top of one slide of a saved template, up to 50 per call and 50 per slide. Requires a Pro account. Use this instead of update_template to place objects: it never touches slots, other slides or other objects. Each item is {type:"text", text, ...}, {type:"shape", shape, text?, ...} or {type:"image", asset, ...}; position and size are optional (a text box or shape lands near the middle, an image is centered and fitted). Shapes: shape is "rect", "roundRect", "ellipse", "line" or "arrow". A new shape starts with a look of its own (an accent fill and centred text for a box; an ink line 4 px wide for a line), so send only what differs. A box shape takes fill, fillOpacity, borderColor, borderWidth, dash, shadow, roundRect also radius (px), and text with the text fields. A line or arrow runs left to right through the middle of its box (turn it with rotate; the arrowhead is at the right end) and takes lineColor, lineWidth, dash; it holds no text. Shapes are native shapes in the PPTX. Coordinates are pixels on a 1920x1080 slide and are kept inside it. A text box's style takes theme colours, "palette:" or "#rrggbb", plus italic, underline, line spacing, fill, border, radius and shadow (see style). Images come only from list_media ids. Set behind:true to put an object under the layout's own title and text (a background picture behind the default title); it is hidden wherever a layout card or panel has a solid fill. All items are added or none. Returns the slide's objects with their ids and the new draft_version. The edit is saved to the template's draft; call publish_template to publish it. Errors: pro_required, not_found, conflict (read again with get_template(draft: true) and retry), invalid_input.

Inputs: objects (required), slide_id (required), template_id (required), expected_version, +1 more.

check_deckCheck deck orderA
Read-onlyIdempotent
Inspect

Validate the slide ORDER of a whole deck before you build it. check_slots looks at one slide's text; this looks at the sequence. Input: layout_ids, the layout of every slide in order. Returns { slide_count, ok, error_count, warning_count, issues[], unknown_layout_ids? }. Each issue has code, severity ("error" must be fixed, "warning" is a quality note), order (slide number), layout_id, message and a one-line fix. Codes: closer_not_last (a closing layout that is not the last slide), repeated_layout (the same layout on consecutive slides). It does not judge whether slides look alike. ok is true when there are no errors.

Inputs: layout_ids (required).

check_slotsCheck slotsA
Read-onlyIdempotent
Inspect

Validate slot text against a layout before rendering. Nothing is rendered and no CSS is returned, so it is cheap: run it on every slide you wrote, fix what it reports, then call render_slide. Input: layout_id and slots (slot id to text), the same as render_slide. Returns { layout_id, ok, error_count, warning_count, issues[] }. Each issue has slot, code (unknown_slot, missing_required, empty_required, too_long, not_filled, blanked), severity ("error" must be fixed, "warning" is a quality note) and a one-line fix. ok is true when there are no errors.

Inputs: slots (required), layout_id (required).

export_pptxExport PPTXAInspect

Turn a deck into a downloadable .pptx file. Requests like "make it a PowerPoint", "PPT로 뽑아줘", or "export this deck" mean this tool. Takes the layout ids and the text for each slot, and returns a signed download link. Coordinates come from our measurements, so the file matches what the gallery shows, but the boxes are fixed, so text longer than slots[].max_chars will be clipped.

Inputs: theme, slides, embed_fonts, template_id.

get_layoutGet layoutA
Read-onlyIdempotent
Inspect

Return one layout as a ready-to-use, self-contained document: HTML, theme CSS, and its slot definitions. Call this once the user knows which layout they want, or with ids returned by suggest_deck.

Inputs: id (required), lang, theme_id.

get_starter_kitGet starter kitA
Read-onlyIdempotent
Inspect

Call this when joining several fetched layouts into one deck file. Requests like "merge these into one file", "bundle it as a deck", or "make it one HTML" mean this tool. Returns the base CSS, assembly rules, spacing tokens, and a viewport snippet for standalone viewing.

Inputs: no named parameters.

get_templateGet templateA
Read-onlyIdempotent
Inspect

Return one saved template: name, theme_id, palette? (the deck palette) and slides as [{id, layout, slots, objects, overrides?}], plus each slide's slot definitions with max_chars. Use it to fill the same structure with new text, then save with update_template or export with export_pptx(template_id), both of which need Pro. To place or change only the objects of one slide, use add_objects, update_objects and remove_objects. Teammates' team templates open here too; those also return new_feedback (open pin comments). A template has a published version (what the share link, the presentation and export_pptx use) and may have a draft (unpublished changes made in the web editor or by update_template). By default you read the published version; pass draft: true to read the draft (the published version when there is no draft), which is what to read before you change a template. The response has published_version, draft_version (0: no draft), has_draft and showing ("published" or "draft"); version is the published version, kept for older callers. Needs an API key; reading works on any plan.

Inputs: id (required), draft.

get_template_feedbackGet template feedbackA
Read-onlyIdempotent
Inspect

Read the pin comments teammates left on a team template. By default only unresolved ones on slides the template still has; pass include_resolved to get every thread. Each thread has the comment id, slide_id and slide_number (null if the slide was deleted), slot (the text slot under the pin, if any), body, author, resolved and replies[]. Use slide_id to match a thread to the slide in get_template, then fix the slide with update_template (keep the slide ids). Resolving a thread is done on the web. Only for templates that belong to the user's team: a personal template answers not_team_template, a template they cannot use not_found. Needs an API key; works on any plan.

Inputs: id (required), include_resolved.

get_themeGet themeA
Read-onlyIdempotent
Inspect

Return one theme in full: its complete CSS and design tokens.

Inputs: id (required).

list_layoutsList layoutsA
Read-onlyIdempotent
Inspect

Search or filter the layout catalog to find a specific layout. Returns metadata only, no HTML. Each entry has position (opener/middle/closer: its role in a deck), when_to_use and when_not_to_use: read them to check the layout fits the content before choosing it. Filter by position to fill a slot of the story, e.g. position "closer" for the last slide. Also the tool for "what is new", "any new layouts?", "what got added since last month" - pass since and it returns only what landed after that date. If the user asked for a whole deck rather than one slide, call suggest_deck first instead of this.

Inputs: lang, limit, query, since, +2 more.

list_mediaList imagesA
Read-onlyIdempotent
Inspect

List the images the user uploaded to their media library on the web: id, name, width, height, aspect_ratio (width/height), bytes, mime and created_at, newest first, plus used_bytes. Pass an id to add_objects to place the picture on a slide. You cannot upload an image or fetch one from a web address; if the picture you need is missing, ask the user to upload it to their media library on the web. Pass scope "team" to list the team library instead (images every team member can use in team templates). Needs an API key; works on any plan.

Inputs: scope.

list_pending_reviewsList pending reviewsA
Read-onlyIdempotent
Inspect

List the review requests ("confirm" requests) in the user's team that are waiting on them: templates whose review is requested or needs a new look because the slides changed after an approval, where the user was picked as a reviewer or has not decided yet. Their own requests are left out. Each item has template_id, name, url, state, version, message, requested_by, requested_at, assigned_to_me and unresolved_feedback. Read the notes on a template with get_template_feedback. Deciding a review (approve or send back) is only possible on the web, so ask the user to do it there. Needs an API key; works on any plan. An account without a team gets an empty list.

Inputs: no named parameters.

list_templatesList templatesA
Read-onlyIdempotent
Inspect

List the templates the user saved in My Templates, and those of the team they belong to: id, name, owner ("personal" or "team"), slide_count, theme_id, source, updated_at, version (the published version; also as published_version) and has_draft (the template has unpublished changes). Team templates also have created_by, review_state and unresolved_feedback (pin comments waiting). Use it to find a template the user refers to, and to read slide_count before appending with update_template. Needs an API key; works on any plan.

Inputs: no named parameters.

list_template_versionsList template versionsA
Read-onlyIdempotent
Inspect

List a template's version history, newest first: version_number, published_at, published_by ("you", a teammate's email, or null), note and slide_count. A version is added each time the template is published (publish_template or the Publish button on the web); the 30 most recent are kept. Restoring a version is done on the web. Needs an API key; works on any plan.

Inputs: id (required).

list_themesList themesA
Read-onlyIdempotent
Inspect

Search or filter the theme catalog. Returns metadata and key colors only, not the full CSS. With an API key, the user's own saved themes (My Themes, id "custom:...") come last with custom: true; their ids work anywhere a theme id does.

Inputs: mood, scheme.

publish_templatePublish templateAInspect

Publish a template's draft: the changes saved by update_template, add_objects, update_objects and remove_objects (or made in the web editor) become the published version, which is what the share link, the presentation, teammates and export_pptx(template_id) show. A new entry is added to the version history; the previous published version stays there and can be restored on the web. Requires a Pro account. Input: the template id, an optional one-line note (up to 100 characters) for the history, and optionally expected_draft_version (the draft_version you last saw) so a draft someone else changed since is not published by mistake. Returns version_number (the history number, v1, v2, ...), published_version and the url. Errors: pro_required, not_found, no_draft (there are no unpublished changes), conflict (the draft changed since expected_draft_version; read it again with get_template(draft: true)), invalid_input.

Inputs: id (required), note, expected_draft_version.

remove_objectsRemove objectsA
Destructive
Inspect

Remove objects from a slide by id. Requires a Pro account. The slide, its slots and the other objects stay. Only objects can be removed here; slides and templates are deleted on the web. If any id is not on the slide, or one is locked (unlock it with update_objects first), nothing is removed. Returns the objects that remain and the new draft_version. The edit is saved to the template's draft; call publish_template to publish it. Errors: pro_required, not_found, conflict (read again with get_template(draft: true) and retry), invalid_input.

Inputs: ids (required), slide_id (required), template_id (required), expected_version, +1 more.

render_slideRender slideA
Read-onlyIdempotent
Inspect

Fill one layout with your text and get back a finished, self-contained HTML document (theme, base and contract CSS inlined) that renders correctly when opened. Use it instead of get_layout when you already know the text: you do not assemble CSS or edit the markup yourself. Input: layout_id, optional theme_id (use the same one for every slide of a deck), slots, lang. Returns { layout_id, theme_id, html, warnings[], ok }. warnings[] lists missing required slots, text over max_chars, unknown slot ids and sample copy left behind, each with a fix; read them and call again after correcting, do not hand the user a slide that has errors. To validate without rendering use check_slots.

Inputs: slots (required), layout_id (required), lang, theme_id.

save_templateSave templateAInspect

Save a deck as a named template in the user's My Templates so it can be reused later. Requires a Pro account; without one the call fails and nothing is saved. Use it after you have built a deck the user wants to keep, for example from suggest_deck. Input: name, optional theme_id (a catalog theme id or custom:), and slides as [{layout, slots}], the same shape export_pptx takes. A template holds 1 to 40 slides on Pro and 1 to 100 on Team. Returns template_id, url (the template's page), slide_count, published_version and draft_version (a new template is published as v1 and has no draft; draft_version is 0), overflow[] (slots whose text is longer than max_chars) and unknown_layouts[]. Pass owner "team" to save it to the user's team instead of their own templates. Deleting is not available here, only on the web. Errors: pro_required, slide_limit, template_limit (the account already has the most templates it can hold), unknown_theme, invalid_input.

Inputs: name (required), slides (required), owner, palette, +1 more.

suggest_deckSuggest deckA
Read-onlyIdempotent
Inspect

Compose a deck and return a preview link the user can open in the browser right away. The user sees what the finished deck looks like without a single file being generated. Use this for requests like "make me a pitch deck", "I need a sales deck", "10 slides for an investor update", "put together a product overview", or "show me a deck outline" - anything where the user has a topic but has not picked layouts yet. ALSO use it when the user already has layouts in hand - "이 레이아웃들 모아서 프리뷰 만들어줘", "combine these layouts into a preview", "추천 프리뷰 만들어줘", "show these together as a deck" - pass them as layout_ids and it returns ONE deck preview link for the whole set. Never answer that kind of request with a list of individual layout links: one deck preview is the deliverable. Returns one theme + a slide order + the preview link, plus a clarify question to put to the user so the composition and theme are their call, not a guess. If order_issues is present in the result, the slide order breaks a rule (closing layout not last, same layout twice in a row): fix it before showing the deck. Always pass the preview link through to the user verbatim, ask clarify.question with its options, and wait for the answer - then call this tool again with deck_id / theme_id as clarify.answer_with says. Do not start generating files while a clarify question is unanswered. Once it is settled, fetch each layout id with get_layout, then call get_starter_kit to join them into one deck.

Inputs: purpose (required), tone, deck_id, theme_id, +2 more.

update_objectsUpdate objectsA
Destructive
Inspect

Change objects already on a slide, by id: position, size, rotation, text, look (font, colour, fill, border, shadow, line), a shape's kind, the image's alt text or picture, stacking order, behind (true sends it behind the layout's own elements, false brings it back in front), group and locked. Requires a Pro account. An object the user locked on the web is refused unless the same change sends locked:false. Send only the fields to change; the style is merged, and a style field sent as null goes back to its default. An image keeps its proportions (send w alone). Up to 50 changes per call, all applied or none. Read ids and the current draft_version with get_template(draft: true). Returns the slide's objects and the new draft_version. The edit is saved to the template's draft; call publish_template to publish it. Errors: pro_required, not_found, conflict (read again with get_template(draft: true) and retry), invalid_input.

Inputs: changes (required), slide_id (required), template_id (required), expected_version, +1 more.

update_templateUpdate templateA
Destructive
Inspect

Change a template the user already saved. The change is saved to the template's draft: the share link, the presentation and export_pptx(template_id) keep showing the published version until you call publish_template. Requires a Pro account; without one the call fails and nothing is changed. Pass the template id and any of: name, theme_id, palette (replaces the deck palette), slides (replaces all slides), or append_slides (adds slides to the end). Read the latest content with get_template(draft: true) first: slides replaces the whole draft. Fields you do not know in what get_template returned (on objects, styles, overrides) must be sent back as they were. Runs (formatting of part of a text): offsets must fit the text sent with them, else invalid_input. When you change a slot's or an object's text and send its runs back exactly as get_template gave them, they are moved with the text (listed in runs_moved); send new runs to set them yourself, or an empty list to remove them. A template holds at most 40 slides on Pro and 100 on Team. If the result would be more than the plan allows, nothing is changed and the response is a slide_limit error that includes how many slides still fit. Call list_templates first to read slide_count when you plan to append. The response has the same fields as save_template, with saved_to "draft", published_version and draft_version. Deleting is not available here, only on the web. To avoid overwriting someone else's edit, pass expected_draft_version (the draft_version from get_template or your last save). If the template already has a draft that was last written by someone other than this API key (the user on the web, or another key), replacing all slides (slides) without expected_draft_version is refused with draft_exists, so a draft you did not read is not overwritten; your own earlier writes do not count, and expected_version does not lift the refusal. append_slides, name and theme changes are not affected. expected_version (the published version) still works for older callers: it fails with conflict if someone has published since. Errors: pro_required, not_found, slide_limit, draft_exists (slides sent without expected_draft_version while a draft that someone else wrote last exists), conflict (the draft changed since expected_draft_version, the published version changed since expected_version, or the draft kept changing during an append; nothing was saved), unknown_theme, invalid_input.

Inputs: id (required), name, slides, palette, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources