Skip to main content
Glama

Restore a thumbnail version

restore_thumbnail_version

Make an earlier version of one option current again: a version number from get_thumbnail, or "original". Appends a copy as the newest version; history is never deleted.

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": {
      "runId": "<runId>",
      "rank": "<rank>",
      "version": "<version>"
    },
    "name": "restore_thumbnail_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankYes
runIdYes
versionYes

Output Schema

NameRequiredDescriptionDefault
rankYes
runIdYes
titleYes
layersNo
webUrlYes
currentYes
editableYes
optionIdYes
originalNo
versionsYes
pendingEditsYes
artifactExpiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is largely pre-supplied. The description still earns credit by disclosing the mechanism beyond those hints: 'Appends a copy as the newest version; history is never deleted.' That clarifies why a non-idempotent mutation is nonetheless non-destructive — useful, but it is a single added fact.

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?

One front-loaded sentence with a colon introducing the argument detail, then a short clause on append semantics. No wasted wording, though the run-on structure packs three distinct facts into a single sentence.

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?

An output schema exists, so return values need no prose, and the append/history behavior covers the main behavioral question for a mutation tool. The remaining gap is 'rank' and 'runId', which are neither in the description nor the schema, so an agent must infer what rank selects.

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 description coverage is 0%, so the description must carry the load. It does well for 'version', explaining both the integer reference to get_thumbnail versions and the 'original' sentinel that matches the anyOf. It says nothing about 'rank' (1-24, presumably which option slot) or 'runId', leaving two of three parameters unexplained.

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?

The description names a specific verb and resource ('Make an earlier version of one option current again') and pins the version universe to values from get_thumbnail or 'original'. It is clearly distinct from editing a thumbnail, though it never explicitly contrasts itself with edit_thumbnail or edit_thumbnail_layers.

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 states the prerequisite source for the version argument (get_thumbnail) and covers the special 'original' value, which is the main usage question an agent would have. It stops short of saying when to prefer this over re-editing the thumbnail, so no exclusions are offered.

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