Skip to main content
Glama

Export PPTX

export_pptx

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_pptx"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoTheme id. Only measured themes work; omit to use the default. A My Theme id ("custom:...") from list_themes also works: its base theme's layout with the user's colors.
slidesNoSlides in order, up to 25 on free, 40 on Pro, 100 on Team. A longer deck is rejected with the limit of the caller's plan. Required unless template_id is given.
embed_fontsNoPut the fonts inside the file so it looks the same where they are not installed. On by default; pass false to leave them out. The result lists fonts that could not be embedded.
template_idNoA saved template id from list_templates. Exports that template with its own theme and slides; theme and slides are then ignored. Errors for it: not_found, template_lookup_failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / slides / description
      Previous value: -"Up to 25 slides, in order. Required unless template_id is given."New value: +"Slides in order, up to 25 on free, 40 on Pro, 100 on Team. A longer deck is rejected with the limit of the caller's plan. Required unless template_id is given."
    • changedInput schema / properties / slides / maxItems
      Previous value: -25New value: +100
  2. Changed1 schema field changed
    • addedInput schema / properties / slides / items / properties / layout / description
      Added value: +"Layout id from list_layouts or suggest_deck."
  3. Changed1 schema field changed
    • changedInput schema / properties / embed_fonts / description
      Previous value: -"Put the fonts inside the file so it looks the same where they are not installed. Off unless set. The result lists fonts that could not be embedded."New value: +"Put the fonts inside the file so it looks the same where they are not installed. On by default; pass false to leave them out. The result lists fonts that could not be embedded."
  4. Changed5 schema fields changed
    • addedInput schema / properties / embed_fonts
      Added value: +{
      +  "description": "Put the fonts inside the file so it looks the same where they are not installed. Off unless set. The result lists fonts that could not be embedded.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / slides / description
      Previous value: -"Up to 25 slides, in order."New value: +"Up to 25 slides, in order. Required unless template_id is given."
    • addedInput schema / properties / template_id
      Added value: +{
      +  "description": "A saved template id from list_templates. Exports that template with its own theme and slides; theme and slides are then ignored. Errors for it: not_found, template_lookup_failed.",
      +  "type": "string"
      +}
    • changedInput schema / properties / theme / description
      Previous value: -"Theme id. Only measured themes work; omit to use the default."New value: +"Theme id. Only measured themes work; omit to use the default. A My Theme id (\"custom:...\") from list_themes also works: its base theme's layout with the user's colors."
    • removedInput schema / required
      Removed value: -[
      -  "slides"
      -]
  5. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations say it is non-read-only, non-destructive, and not idempotent, so the description does not need to explain side effects. It adds real context: a signed download link is returned, box coordinates come from measurements so the output matches the gallery, and text longer than slots[].max_chars is clipped. That clipping disclosure is exactly the kind of caveat annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action, then the triggering phrases, then the input shape, then the output and constraint. Every sentence carries information, though the mixed-language phrase list is slightly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by stating the return value is a signed download link. It also flags the clipping limitation, which is the main failure mode a caller must know. Per-plan slide limits and template error codes are documented in the schema, so no critical gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents theme, slides, embed_fonts, and template_id in detail. The description only reinforces the layout-id-plus-slot-text model and the max_chars clipping consequence, adding little beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: turn a deck into a downloadable .pptx file. It is clearly distinguishable from render_slide (a preview) and save_template (storing a template) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete trigger phrases ("make it a PowerPoint", "PPT로 뽑아줘", "export this deck") so the agent can map user intent to this tool even across languages. It stops short of naming when not to use it, e.g. render_slide for images or save_template for reuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources