Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-indexed)
tokenYesAsset token
per_pageNoItems per page (1-100, default 100)
organizationNoWorkspace 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.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses plan-dependent gating (Free/Pro: primary_gcs_id null and thumbnails empty for versions older than the revert window), that reads are always available regardless of plan, and that md5 may be a storage-placeholder for async uploads.

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?

Front-loaded with the 'entry point' statement and otherwise dense with useful facts, though it is on the long side and packs a wall of field names into one sentence. Nearly every clause earns its place, but the field enumeration could be trimmed.

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 carries the full burden of describing the return shape and does so thoroughly (version_number, md5, size, media_type, source, comment, created_at, created_by_token, revertable, thumbnails, head_version_number), plus the plan-gating caveat and a pointer to display_url for current content.

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 in the schema; the description adds no pagination or parameter guidance. Its detail is instead directed at return fields, which is not what this dimension measures, so the baseline 3 applies.

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 states a specific verb and resource ('Lists the version history of an asset, newest first') and scopes it broadly as 'the entry point for anything about an asset's earlier states'. It explicitly names the sibling tools it feeds into (revert_asset, edit_asset_version_comment), so an agent can place it relative to alternatives 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 tells the agent exactly when to reach for this tool (version history, previous/older versions, what changed and when, choosing a version to restore) and names the downstream alternatives with their purpose. The follow-on routing to revert_asset for rollback and edit_asset_version_comment for annotation is explicit rather than inferred.

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

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