getdeck

Update template

update_template

Change a template the user already saved. Requires a Pro account; without one the call fails and nothing is changed. Pass the template id and any of: name, theme_id, slides (replaces all slides), or append_slides (adds slides to the end). A template holds at most 25 slides. If the result would be more than 25, 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. Deleting is not available here, only on the web. Errors: pro_required, not_found, slide_limit, conflict (the template changed since expected_version, or kept changing during an append; nothing was saved), unknown_theme, invalid_input.

Input Schema

Name	Required	Description
`id`	Yes
`name`	No
`slides`	No
`theme_id`	No
`append_slides`	No
`expected_version`	No	The version from get_template or a previous save. Given, the call fails with conflict if the template changed since.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 23, 2026

addedInput schema / properties / append_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 / append_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 / append_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"
+}

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 burden and does so: Pro gating, atomic all-or-nothing semantics ("nothing is changed"), the 25-slide cap with a slide_limit error that reports remaining capacity, and conflict semantics around expected_version. It also discloses the response shape ("same fields as save_template") and enumerates every error code with meaning.

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

Conciseness5/5

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

Front-loaded with the action and the account precondition, then the mutation modes, then limits, then the error list. Every sentence adds a distinct operational fact; nothing is restated from the schema.

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 six-parameter mutation tool with no annotations and no output schema, the definition covers preconditions, atomicity, limits, concurrency, return shape, and error handling. An agent can call this correctly and recover from failures without further documentation.

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

Parameters5/5

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

Top-level schema coverage is only 17%, yet the description supplies the missing semantics for the critical parameters: slides replaces all slides, append_slides appends, and the conflict behavior of expected_version. The replacement-vs-append distinction is not derivable from the schema and is the main correctness risk here.

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 specific verb and resource plus a scope constraint: "Change a template the user already saved," which implicitly separates it from save_template (creation). It never names save_template or get_template as alternatives for routing, so sibling differentiation is inferred rather than stated.

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?

Explicit when-to-use and when-not: requires Pro (with failure behavior), "Call list_templates first to read slide_count when you plan to append," and "Deleting is not available here, only on the web." It also distinguishes the two ways to change slides (slides replaces all vs append_slides adds to the end).

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?