Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

List template versions

listTemplateVersions
Read-only

The versions of one template, newest first, a page at a time, as the version history of the template editor lists them: each one’s number, whether it is a draft or published, its engine, its subject and when it was published. Name the template by id (tpl_…) or slug. Says which version sends resolve to and which is the draft being edited. getTemplateVersion reads the body of one of them.

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": "listTemplateVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses ordering (newest first), paging behavior, and the exact informational payload per row: version number, draft vs published status, engine, subject, publish time, plus which version sends resolve to and which is the draft being edited. That is material context an agent cannot infer from structured fields.

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 what the tool returns and its ordering before the identifier and the sibling pointer; every sentence carries information. Slightly dense — the clause 'as the version history of the template editor lists them' is decorative and could be dropped.

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

Completeness4/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 correctly spends its budget describing the shape of returned rows and the special markers (send version vs draft). It is nearly complete for a 3-param read tool; only cursor/limit semantics remain unaddressed.

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 0%, so the description must compensate — it does for `id` by revealing the accepted format ('tpl_…' or slug), which the schema only types as a string. But `limit` and `cursor` get no mention beyond the phrase 'a page at a time'; there is no statement that cursor is an opaque continuation token or that limit caps page size.

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+resource ('The versions of one template'), plus ordering ('newest first') and shape ('a page at a time'). It clearly separates itself from getTemplateVersion by noting that tool reads the body of one version rather than listing them.

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?

It names the alternative (getTemplateVersion) and its distinct purpose, so the agent can route between listing versions and fetching a version body. It stops short of explicit 'do not use this when…' exclusions, e.g. for deleted versions or how it relates to listTemplateSends.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources