Skip to main content
Glama

Get template

get_template
Read-onlyIdempotent

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.

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": {
      "id": "<id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate id from list_templates.
draftNotrue: read the draft (the latest changes). Default false: the published version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / draft
      Added value: +{
      +  "description": "true: read the draft (the latest changes). Default false: the published version.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Template id from list_templates."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial non-obvious context: templates have a published version and an optional draft, reads default to published, the draft read falls back to published when no draft exists, and teammates' team templates return extra new_feedback pin comments. It also discloses plan/credential requirements (API key; writing/exporting needs Pro, reading works on any plan).

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 the return shape in the first sentence, then layers workflow, alternatives, versioning, and response fields in a logical order. It is dense and long, and the trailing note about 'version is the published version, kept for older callers' is legacy detail an agent rarely needs, but nearly every sentence carries real 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?

There is no output schema, so the description carries the burden of explaining return values and does so completely: response fields published_version, draft_version (0 meaning none), has_draft, showing, plus per-slide slot max_chars. Combined with the versioning model and auth notes, nothing needed to call this correctly is missing.

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 baseline is 3; the description goes further by explaining the semantics of draft: true (reads the latest changes, falls back to published when there is no draft) and when to use it. The id parameter's provenance is only in the schema ('from list_templates'), so it does not add much there.

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?

Uses a specific verb and resource ('Return one saved template') and immediately enumerates the returned shape (name, theme_id, palette?, slides with id/layout/slots/objects/overrides, slot definitions with max_chars). It also distinguishes itself from single-slide object tools (add_objects/update_objects/remove_objects), so an agent can tell it apart from siblings like get_layout or list_templates.

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?

States the intended workflow explicitly (read to fill the structure with new text, then update_template or export_pptx), names the alternatives for other jobs (add_objects/update_objects/remove_objects for one slide's objects), and gives a conditional rule: pass draft: true 'before you change a template'. When-not guidance and prerequisites (Pro for save/export, API key) are all present.

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