Skip to main content
Glama

Show thumbnail gallery

show_thumbnails
Read-onlyIdempotent

Display an inline gallery of an existing run's CURRENT thumbnails, titles, hooks and HD/4K downloads. Call after a full run finishes, after an edit finishes, or when the user asks to see or check earlier results ("show me", "how did my last one turn out"); find the run with list_generations. Optional ranks select options. Reads only; never generates images or consumes generation/edit allowance. Refreshes expiring links.

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

Input Schema

NameRequiredDescriptionDefault
ranksNo
runIdYes

Output Schema

NameRequiredDescriptionDefault
modeNo
errorNo
runIdYes
configNo
statusYes
webUrlYes
optionsNo
progressNo
projectIdYes
allFlaggedNo
packagingUrlNo
pollAfterSecondsNo
artifactExpiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already establish readOnlyHint, idempotentHint and destructiveHint=false, and the description still adds substantive information beyond them: it confirms no image generation occurs and no generation/edit allowance is consumed, and it notes that the call refreshes expiring links. Saying the gallery shows CURRENT results also tells the agent that the output reflects the latest state after edits, which the annotations do not convey.

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?

Three dense sentences ordered from purpose to triggers to behavior, with zero filler. The user-phrase examples ('show me', 'how did my last one turn out') are the only expansion, and they earn their place because they help match intent.

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 an output schema present, a returning-gallery tool does not need to describe its return values, and the four annotations plus the 'reads only / no allowance' caveat cover the safety profile. The remaining gap is the ranks parameter, whose selection semantics are left undefined, and that is the only thing preventing an agent from having a full picture before calling.

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 full burden of explaining the parameters, and it only partly does: 'Optional ranks select options' explains what ranks does, but not its 1-24 range, whether it limits or orders the selection, or what the 3-item cap means. runId is never explicitly defined, though 'find the run with list_generations' implies it identifies the run, so the description adds some meaning but not enough.

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?

The description names a specific verb (Display) and resource (an inline gallery of an existing run's CURRENT thumbnails, titles, hooks and HD/4K downloads), and by saying it targets an existing run's current state, it sets itself apart from artifact-producing siblings like create_generation and from the single-item get_thumbnail.

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 gives clear trigger conditions ('after a full run finishes, after an edit finishes, or when the user asks to see or check earlier results') and provides a discovery path for the required runId ('find the run with list_generations'). What it does not state is when not to use it, e.g. when to use get_thumbnail for a single thumbnail instead of this gallery, so it falls short of full alternative routing.

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