Skip to main content
Glama

List template versions

list_template_versions
Read-onlyIdempotent

List a template's version history, newest first: version_number, published_at, published_by ("you", a teammate's email, or null), note and slide_count. A version is added each time the template is published (publish_template or the Publish button on the web); the 30 most recent are kept. Restoring a version is done on the web. Needs an API key; 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": "list_template_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate id from list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, but the description adds substantial context beyond them: a hard retention cap of the 30 most recent versions, newest-first ordering, what published_by values mean ("you", teammate email, or null), the API-key requirement, and plan availability. These are exactly the operational constraints an agent needs.

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?

Four dense sentences, front-loaded with the action and return shape, then provenance, retention, out-of-scope operations, and access requirements. Nothing is repeated and every clause adds usable 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?

With no output schema, the description compensates by enumerating the returned fields and their semantics, plus ordering, retention limits, auth, and plan scope. For a single-parameter read tool, an agent has everything needed to call it correctly and interpret results.

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% and the single id parameter is already documented as coming from list_templates, so the schema carries the parameter burden. The description adds no further meaning about the id beyond what the schema states, making the baseline 3 appropriate.

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 (list a template's version history) plus the ordering (newest first) and the exact fields returned (version_number, published_at, published_by, note, slide_count). This clearly distinguishes it from list_templates, which enumerates templates rather than their versions.

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?

Gives clear operational context: versions arise from publish_template or the web Publish button, and restoring a version is explicitly out of scope on the web. It does not explicitly route the agent elsewhere for the template's current content (e.g. get_template), so it stops short of full when/when-not guidance.

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