Skip to main content
Glama
Sign In

Playbook

by com.playbook
OverviewDiscussionsAdmin

List hosted app versions

list_app_versions
Read-only

List the kept versions of a hosted app, newest first; Playbook keeps the last 50. Each has a number, created_at, created_by, file_count, bytes, comment and, for a rollback, reverted_from_number. Also returns head_version_number, the version that is live. Read a version's files with get_app_source and put one back live with revert_app.

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": {
      "slug": "<slug>"
    },
    "name": "list_app_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug of the app, from list_apps
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. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description adds genuinely new behavior: Playbook retains only the last 50 versions, results come newest first, and head_version_number identifies the live version. The retention limit is exactly the kind of non-obvious constraint an agent cannot get 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses: purpose and ordering first, then return fields, then next-step tools. No redundant restatement of the title, and each sentence carries distinct 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 no output schema, the description compensates by enumerating the returned fields (number, created_at, created_by, file_count, bytes, comment, reverted_from_number, head_version_number) and explaining the rollback marker. Combined with the retention note and sibling pointers, an agent has everything needed to call it and interpret the result.

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% and both parameters (slug, organization) are already documented in detail, including the single-workspace omission rule. The description adds no parameter-level meaning, so the baseline of 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?

States a specific verb and resource ('List the kept versions of a hosted app') along with ordering ('newest first') and retention scope ('keeps the last 50'). This clearly separates it from list_apps (apps, not versions) and from get_app_source (files, not version metadata).

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?

Explicitly routes the agent to the right follow-up siblings: get_app_source to read a version's files and revert_app to put one back live. It gives clear positive context but no exclusion such as when to skip listing or whether pagination/limits apply, so it stops just short of a 5.

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