blink artifact

List versions

versions_list

Read-only

List the saved versions (history snapshots) of an artifact, newest first (any role can read): { id, rev, versions: [{ id, at ISO, rev, reason (auto, agent = taken before an agent write after people edited, restore = taken before a restore), by [{ name, agent }], pinned? }] }. A version's rev can be compared with changes_since. Pass a version id to version_restore.

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

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile, yet the description adds substantial context: role requirements ('any role can read'), sort order, the full return shape, and non-obvious semantics for the 'reason' values (auto, agent = snapshot before an agent write after people edits, restore = snapshot before a restore). That reason-code explanation is knowledge an agent could not derive anywhere else.

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?

Purpose and scope are front-loaded in the first clause, and every element (ordering, return shape, reason codes, sibling routing) is load-bearing. The inline brace-delimited shape dump is dense and slightly hurts readability, but it carries real 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 only one parameter and no output schema, the description supplies the return structure, field meanings, permission model, and next-step routing. Nothing an agent needs in order to call this correctly is missing.

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% and the single 'id' property is an undescribed string, so the description carries the burden. It implies the id is an artifact id via 'of an artifact', but never explicitly says so, and it mentions a distinct 'version id' for version_restore without clarifying that this tool does not take one — a small ambiguity.

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 the saved versions (history snapshots) of an artifact') plus ordering semantics ('newest first'), which is exactly what an agent needs to distinguish this read from version_restore and changes_since.

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?

'(any role can read)' establishes access preconditions, and the closing lines route to alternatives: 'A version's rev can be compared with changes_since. Pass a version id to version_restore.' The routing is clear but implicit — it never states an explicit 'use this tool when you need X instead of Y' exclusion.

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

All blink artifact tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?