Simpler.Asia

studio.list_versions

Read-only

List a studio project's stored versions, newest first: {version, created_at, label, current}, plus every named version (snapshots) and how many of the 20 names are used. A project keeps its newest 20 saved versions, one per 10 minutes for the last day, one per day for the last 30 days, and every named snapshot (up to 20); older unnamed versions are deleted. Refuses: a project_id outside your scope (NOT_FOUND): studio_project_list lists your projects; pass one of their ids; a limit outside 1 to 50 (VALIDATION_ERROR): pass a smaller limit. Free; reads only.

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": {
      "project_id": "<project_id>"
    },
    "name": "studio.list_versions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many of the newest versions to return (default 20). Named versions are always all listed under snapshots.
`project_id`	Yes	The studio project (vp_...) whose history to use.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing retention behavior: newest 20 saved versions, 10-minute cadence for one day, daily for 30 days, all named snapshots up to 20, and deletion of older unnamed versions. It also states the tool is free and reads only, and documents the error conditions.

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?

The description is dense and front-loads the core purpose, returned fields, and retention rules before the error cases. It is longer than minimal, but most sentences add operational value rather than restating the name.

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 no output schema, the description compensates by naming the returned fields and snapshot summary shape, and it covers retention, validation failures, and scope errors. An agent has enough information to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds useful meaning: limit controls how many newest versions are returned while named versions are always listed under snapshots, and project_id must be within scope. This enriches parameter behavior beyond the schema text.

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 a studio project's stored versions') and immediately specifies ordering and returned fields. It is clearly distinguishable from mutation siblings like restore_version or snapshot_version.

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?

Explains when the tool applies by describing the version history it returns, and explicitly routes the agent to studio_project_list when it lacks a valid project_id. It also documents validation failure handling for limit, though it does not compare against sibling tools beyond that error path.

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

All Simpler.Asia 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?