Playbook

List asset versions

list_asset_versions

Read-only

The entry point for anything about an asset's earlier states — version history, previous or older versions, what changed and when, and picking one to restore or roll back to with revert_asset (annotate one with edit_asset_version_comment). Lists the version history of an asset, newest first. Each version has a version_number (the key to revert to or annotate), md5 (content md5; may be a storage-placeholder value for async uploads), size, media_type, source (UPLOAD or REVERT), comment, created_at, created_by_token, a revertable flag, and thumbnails. Also returns head_version_number — the number the next version write will take (1 for a never-versioned asset). Reads are always available regardless of plan. On Free/Pro plans, versions older than the revert window are gated: primary_gcs_id is null and thumbnails is empty (the full-resolution original is not available on those plans). Use the live asset's display_url to preview current content.

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": {
      "token": "<token>"
    },
    "name": "list_asset_versions"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (1-indexed)
`token`	Yes	Asset token
`per_page`	No	Items per page (1-100, default 100)
`organization`	No	Workspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "token",
-  "context"
-]New value: +[
+  "token"
+]

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only carry readOnlyHint/destructiveHint/openWorldHint; the description goes well beyond them by disclosing ordering (newest first), the plan-gating behavior (older-than-revert-window versions have primary_gcs_id null and empty thumbnails on Free/Pro), the md5 storage-placeholder caveat for async uploads, and that reads are always available regardless of plan. That is exactly the kind of behavior an agent cannot infer from structured fields.

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 is front-loaded in the first clause and the rest is substantive, but the opening sentence is keyword-stuffed ('version history, previous or older versions, what changed and when') and parenthetical asides interrupt the flow. Because no output schema exists, the field enumeration earns its space, so the minor bloat is tolerable.

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 enumerating every returned field (version_number, md5, size, media_type, source, comment, created_at, created_by_token, revertable, thumbnails) plus head_version_number and its meaning. Combined with the plan-gating caveat, an agent has everything needed to call this and interpret the result correctly.

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 100%, so page, per_page, token, and organization are already documented, including the workspace-resolution nuance. The description adds no further meaning about pagination defaults, token format, or workspace selection beyond what the schema states, which is the appropriate baseline when the schema does the work.

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?

Specific verb + resource ('Lists the version history of an asset, newest first') with explicit scope, and it distinguishes itself from siblings by naming revert_asset and edit_asset_version_comment as the downstream actions. An agent can tell this apart from get_asset, list_assets, or create_asset_version without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It positions itself as 'the entry point for anything about an asset's earlier states' and enumerates the triggering intents (history, previous/older versions, what changed and when). It also routes explicitly: use revert_asset to restore, edit_asset_version_comment to annotate, and the live asset's display_url to preview current content — a clear when-to-use/when-to-use-something-else mapping.

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

All Playbook 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?