getdeck

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 25 slides. Returns template_id, url (the template's page), slide_count, version (use it as expected_version in update_template), overflow[] (slots whose text is longer than max_chars) and unknown_layouts[]. 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.

Input Schema

Name	Required	Description	Default
`name`	Yes
`slides`	Yes
`theme_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

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"
+}

AddedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full load and does so: Pro gating and its failure behavior, the 1-to-25 slide bound, the returned fields (template_id, url, slide_count, version, overflow[], unknown_layouts[]) and their downstream use (version as expected_version). It even enumerates error codes including template_limit and pro_required.

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-loads purpose, then prerequisites, inputs, outputs, and errors in that order. It is dense but every clause is informational; the input/output/errors run-on sentences could be broken up slightly for readability.

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?

No output schema and no annotations exist, yet the description explains return values, error modes, account requirements, and the fact that deletion lives elsewhere. An agent has everything needed to decide and invoke correctly.

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?

Top-level schema parameters have no descriptions (reported 0% coverage), and the description fills the most important gaps: theme_id accepts a catalog theme id or 'custom:<uuid>', slides use the same [{layout, slots}] shape as export_pptx, and the slide count is bounded. It does not explain the required name constraints or the interplay of objects/overrides, though the nested schema already documents those richly.

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?

States a specific verb and resource: saving a deck as a named template in the user's My Templates, with the reuse motivation. It is clearly distinguishable from siblings—update_template is referenced via the returned version, and deletion is explicitly routed to the web rather than a sibling tool.

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

Usage Guidelines5/5

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

Gives timing ('after you have built a deck the user wants to keep, for example from suggest_deck'), a prerequisite ('Requires a Pro account; without one the call fails and nothing is saved'), and excludes a capability ('Deleting is not available here, only on the web'). No inference is required.

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

All getdeck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?