Skip to main content
Glama

Get thumbnail versions and layers

get_thumbnail
Read-onlyIdempotent

Read one option (runId + rank) for editing: current links, version history, edits in progress, and for Editable runs its text and image layers with indexes for edit_thumbnail_layers. Poll it after starting an edit.

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>"
    },
    "name": "get_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
rankYes
runIdYes

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's genuinely additive content is that the call reflects an evolving state needing polling after an edit starts, which hints at eventual consistency. It does not state caching, latency, or failure behavior for an unknown runId/rank.

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?

Two short sentences, front-loaded with the selector, then the payload list, then the polling instruction. The middle run of comma-separated payload items is dense but each item is informative. No filler sentences.

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 description covers the key behavioral points: per-option scope, layer indexes for edit_thumbnail_layers, and post-edit polling. Given only two parameters and rich annotations, the remaining gap is the missing explanation of runId/rank semantics.

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 parameter meaning, and it only links 'rank' implicitly to 'one option' and 'runId' to a run selector. It never explains what a run is here or what rank 1–24 indexes into, so a caller still learns more from the schema's constraints than from the prose.

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 object: 'Read one option (runId + rank)' and enumerates the payload — current links, version history, edits in progress, text/image layers. That is well beyond a tautology and tells the agent this is a per-option detail fetch, not a listing. It stops short of a 5 because the wording 'one option' is slightly oblique and no sibling other than edit_thumbnail_layers is explicitly differentiated.

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 two concrete usage cues: it is 'for editing' and 'Poll it after starting an edit', which tells the agent when in a workflow to call it. It also points at edit_thumbnail_layers as the consumer of the layer indexes. No explicit when-not guidance or named alternative for non-edit reads is given.

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