Skip to main content
Glama

Save template

save_template

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "slides": "<slides>"
    },
    "name": "save_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTemplate name shown in My Templates.
ownerNoWhere to save it. Default "personal". "team" saves it to the user's team (they must be an active member), where teammates can open, comment on and review it. Images in a team template must come from the team library (list_media with scope "team").
slidesYesThe slides, in order: [{layout, slots}]. Up to 40 on Pro, 100 on Team.
paletteNoThe template's deck palette: up to 64 entries [{ "name": "Brand red", "color": "#c8102e" }]. Names are 1-40 letters, digits, spaces, "_" or "-", unique (ignoring case). Elements point at an entry with "palette:<name>". Sending palette replaces the whole list; null or [] removes it. Leave it out to keep it as it is.
theme_idNoA catalog theme id or custom:<uuid>. Omit to use the default theme.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / palette
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "color": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "color"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The template's deck palette: up to 64 entries [{ \"name\": \"Brand red\", \"color\": \"#c8102e\" }]. Names are 1-40 letters, digits, spaces, \"_\" or \"-\", unique (ignoring case). Elements point at an entry with \"palette:<name>\". Sending palette replaces the whole list; null or [] removes it. Leave it out to keep it as it is."
      +}
    • addedInput schema / properties / slides / items / properties / objects / items / properties / group
      Added value: +{
      +  "description": "Objects with the same group id move and copy together in the web editor; keep it when you resend.",
      +  "type": "string"
      +}
    • addedInput schema / properties / slides / items / properties / objects / items / properties / locked
      Added value: +{
      +  "description": "true: the user locked it on the web; keep it when you resend.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / slides / items / properties / objects / items / properties / runs
      Added value: +{
      +  "description": "For type \"text\". Formatting of part of the text: [{ start, end, bold?, italic?, underline?, color?, link? }]. start and end are UTF-16 offsets into the text (JavaScript string indices: a Korean syllable counts 1, an emoji outside the basic plane 2), end exclusive, start < end. bold, italic, underline are true or false (false undoes a look the whole text has); color takes the colour forms below; link is kept for a later version and not drawn yet. The text itself stays plain. Ranges must fit the text, else the call fails with invalid_input. Shown in the editor, the PPTX (one text run per piece) and the HTML export. Changing the text without sending runs moves the stored runs with it (text before a range shifts it; a range whose characters are all deleted is dropped); send runs with the text to set them yourself, null (update_objects) or [] to remove them. Fields you do not know on a run are kept.",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "end": {
      +        "type": "number"
      +      },
      +      "start": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "start",
      +      "end"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / slides / items / properties / objects / items / properties / shape
      Added value: +{
      +  "description": "For type \"shape\": \"rect\", \"roundRect\", \"ellipse\", \"line\" or \"arrow\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / slides / items / properties / objects / items / properties / style / description
      Added value: +"For type \"text\" and \"shape\". Look fields (all optional; send null to take one away and go back to the default): text: size (8-400 px; in an override entry it is called fontSize), weight (400 or 700), italic, underline, strike (true/false), align (\"left\", \"center\", \"right\"), lineHeight (multiple of the size, 0.5-4), vAlign (\"top\", \"middle\", \"bottom\"; text boxes only), color. box: fill (a colour or \"none\"), fillOpacity (0-1), borderColor, borderWidth (0-40 px), radius (0-540 px), shadow (\"none\", \"sm\", \"md\", \"lg\"). line (strokes of a drawn line or icon): lineColor, lineWidth (0.5-40 px), dash (\"solid\", \"dash\", \"dot\"; also the border's style). A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme. Some layout elements are drawn as a picture in the PPTX; colours stored for them are ignored on every output."
    • changedInput schema / properties / slides / items / properties / objects / items / properties / style / properties / color / description
      Previous value: -"A theme token name such as \"ink\" or \"accent\", not a color value."New value: +"A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme."
    • changedInput schema / properties / slides / items / properties / objects / items / properties / text / description
      Previous value: -"For type \"text\"."New value: +"For type \"text\", and a box shape's inner text."
    • changedInput schema / properties / slides / items / properties / objects / items / properties / type / description
      Previous value: -"\"image\" or \"text\"."New value: +"\"image\", \"text\" or \"shape\"."
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / description
      Added value: +"Only what changed. Look fields (all optional; send null to take one away and go back to the default): text: size (8-400 px; in an override entry it is called fontSize), weight (400 or 700), italic, underline, strike (true/false), align (\"left\", \"center\", \"right\"), lineHeight (multiple of the size, 0.5-4), vAlign (\"top\", \"middle\", \"bottom\"; text boxes only), color. box: fill (a colour or \"none\"), fillOpacity (0-1), borderColor, borderWidth (0-40 px), radius (0-540 px), shadow (\"none\", \"sm\", \"md\", \"lg\"). line (strokes of a drawn line or icon): lineColor, lineWidth (0.5-40 px), dash (\"solid\", \"dash\", \"dot\"; also the border's style). A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme. Some layout elements are drawn as a picture in the PPTX; colours stored for them are ignored on every output."
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / properties / color
      Added value: +{
      +  "description": "A colour is one of: a theme colour token (ink, ink-soft, ink-muted, ink-on-dark, accent, accent-soft, accent-bg, bg, bg-alt, bg-inverse, border, border-strong, success, warning, danger), which follows the theme; \"palette:<name>\" for an entry of the template's deck palette, which follows that entry; or a direct colour \"#rrggbb\" (no alpha; use fillOpacity for a see-through fill). Palette and direct colours stay when the theme changes, also with a custom theme.",
      +  "type": "string"
      +}
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / properties / fill
      Added value: +{
      +  "description": "Box fill: a colour, or \"none\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / properties / fontSize
      Added value: +{
      +  "description": "Text size in px, 8 to 400.",
      +  "type": "number"
      +}
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / properties / locked
      Added value: +{
      +  "description": "true: the user locked the element on the web (no effect on the look or the export); keep it when you resend.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / slides / items / properties / overrides / additionalProperties / properties / runs
      Added value: +{
      +  "description": "For a text slot element. Formatting of part of the text: [{ start, end, bold?, italic?, underline?, color?, link? }]. start and end are UTF-16 offsets into the text (JavaScript string indices: a Korean syllable counts 1, an emoji outside the basic plane 2), end exclusive, start < end. bold, italic, underline are true or false (false undoes a look the whole text has); color takes the colour forms below; link is kept for a later version and not drawn yet. The text itself stays plain. Ranges must fit the text, else the call fails with invalid_input. Shown in the editor, the PPTX (one text run per piece) and the HTML export. Changing the text without sending runs moves the stored runs with it (text before a range shifts it; a range whose characters are all deleted is dropped); send runs with the text to set them yourself, null (update_objects) or [] to remove them. Fields you do not know on a run are kept.",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "end": {
      +        "type": "number"
      +      },
      +      "start": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "start",
      +      "end"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / slides / items / properties / overrides / description
      Previous value: -"Changes to the layout's own elements, by element key: { \"top-accent-bar\": { \"deleted\": true }, \"title\": { \"x\": 40, \"y\": 62 } }. Only the values that changed are given; x, y, w, h are pixels on the 1920x1080 slide and the rest stays as the layout draws it. Resend the overrides you got from get_template or they are removed. Requires Pro."New value: +"Changes to the layout's own elements, by element key: { \"top-accent-bar\": { \"deleted\": true }, \"title\": { \"x\": 40, \"y\": 62, \"color\": \"#c8102e\", \"italic\": true } }. Only the values that changed are given; x, y, w, h are pixels on the 1920x1080 slide and the rest stays as the layout draws it. Look fields (colour, fill, border, line spacing...) sit in the same entry; see the entry schema. Resend the overrides you got from get_template or they are removed. Requires Pro."
  2. Changed1 schema field changed
    • changedInput schema / properties / slides / description
      Previous value: -"The slides, in order: [{layout, slots}]. 1 to 25."New value: +"The slides, in order: [{layout, slots}]. Up to 40 on Pro, 100 on Team."
  3. Changed4 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Template name shown in My Templates."
    • addedInput schema / properties / slides / description
      Added value: +"The slides, in order: [{layout, slots}]. 1 to 25."
    • addedInput schema / properties / slides / items / properties / layout / description
      Added value: +"Layout id from list_layouts or suggest_deck."
    • addedInput schema / properties / theme_id / description
      Added value: +"A catalog theme id or custom:<uuid>. Omit to use the default theme."
  4. Changed1 schema field changed
    • addedInput schema / properties / owner
      Added value: +{
      +  "description": "Where to save it. Default \"personal\". \"team\" saves it to the user's team (they must be an active member), where teammates can open, comment on and review it. Images in a team template must come from the team library (list_media with scope \"team\").",
      +  "enum": [
      +    "personal",
      +    "team"
      +  ],
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / slides / items / properties / id
      Added value: +{
      +  "description": "The slide's id from get_template. Keep it when you resend a slide; leave it out for a new slide and the server assigns one.",
      +  "type": "string"
      +}
    • addedInput schema / properties / slides / items / properties / objects
      Added value: +{
      +  "description": "Images and text boxes laid over the slide, in 1920x1080 pixels. Resend the objects you got from get_template or they are removed. At most 50 per slide.",
      +  "items": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "alt": {
      +        "description": "For type \"image\": a short description of the picture for screen readers (up to 300 characters).",
      +        "type": "string"
      +      },
      +      "asset": {
      +        "description": "For type \"image\": the id of an image in the user's media library.",
      +        "type": "string"
      +      },
      +      "behind": {
      +        "description": "true: drawn behind the layout's own elements, on top of the slide background. Absent or false: in front of the layout.",
      +        "type": "boolean"
      +      },
      +      "h": {
      +        "type": "number"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "rotate": {
      +        "type": "number"
      +      },
      +      "style": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "align": {
      +            "type": "string"
      +          },
      +          "color": {
      +            "description": "A theme token name such as \"ink\" or \"accent\", not a color value.",
      +            "type": "string"
      +          },
      +          "size": {
      +            "type": "number"
      +          },
      +          "weight": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "text": {
      +        "description": "For type \"text\".",
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "\"image\" or \"text\".",
      +        "type": "string"
      +      },
      +      "w": {
      +        "type": "number"
      +      },
      +      "x": {
      +        "type": "number"
      +      },
      +      "y": {
      +        "type": "number"
      +      },
      +      "z": {
      +        "description": "Stacking order; larger is in front. Each layer (see behind) is ordered on its own.",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "x",
      +      "y",
      +      "w",
      +      "h",
      +      "z"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / slides / items / properties / overrides
      Added value: +{
      +  "additionalProperties": {
      +    "additionalProperties": {},
      +    "properties": {
      +      "deleted": {
      +        "description": "true: the element is not drawn on this slide (not in the export either).",
      +        "type": "boolean"
      +      },
      +      "h": {
      +        "type": "number"
      +      },
      +      "w": {
      +        "type": "number"
      +      },
      +      "x": {
      +        "type": "number"
      +      },
      +      "y": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "description": "Changes to the layout's own elements, by element key: { \"top-accent-bar\": { \"deleted\": true }, \"title\": { \"x\": 40, \"y\": 62 } }. Only the values that changed are given; x, y, w, h are pixels on the 1920x1080 slide and the rest stays as the layout draws it. Resend the overrides you got from get_template or they are removed. Requires Pro.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  6. Added

TDQS

A4.3/5.0
Behavior5/5

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

With annotations supplying only the safety profile, the description goes well beyond them: a Pro account prerequisite with defined failure ('the call fails and nothing is saved'), slide count limits per plan, the full return shape including published_version/draft_version semantics, overflow[] and unknown_layouts[]. It also names the error codes (pro_required, slide_limit, template_limit, unknown_theme, invalid_input), which is exactly the behavioral detail annotations cannot convey.

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?

Front-loaded with the action and precondition, then inputs, returns, and errors in a logical order with no filler prose. There is minor redundancy: the 1-40 / 1-100 slide limits repeat what the slides schema already states, and the error enumeration is dense, but every element still carries information.

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

Completeness5/5

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

For a mutating create tool with no output schema and no annotations covering behavior, the description covers prerequisites, failure modes, limits, return payload fields, and a non-obvious option (owner='team'). An agent has everything needed to decide whether to call it and how to interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real cross-tool meaning by saying slides are 'the same shape export_pptx takes' and clarifying theme_id accepts 'a catalog theme id or custom:<uuid>'. It also restates the owner='team' behavior, which is redundant with the schema but harmless. The cross-reference to export_pptx is the kind of transfer an agent cannot get from the schema alone.

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

Purpose4/5

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

States a concrete verb and resource: 'Save a deck as a named template in the user's My Templates so it can be reused later.' That is unambiguous about what is created and where. It does not explicitly differentiate itself from siblings such as update_template or publish_template, so an agent must still infer from names alone whether this creates versus modifies a template.

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?

'Use it after you have built a deck the user wants to keep, for example from suggest_deck' gives a clear triggering context, and 'Pass owner "team" to save it to the user's team instead of their own templates' plus 'Deleting is not available here, only on the web' set boundaries. What is missing is an explicit when-not-to-use case, e.g. how it relates to update_template when the template already exists.

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