Skip to main content
Glama

List Hosted App versions

list_app_versions
Read-onlyIdempotent

List an app's immutable versions newest first, including hash, publisher, time, file count, bytes, current flag and aligned request_ids and request_names sorted by name then ID, plus aligned calls_without_grant_ids and calls_without_grant_names sorted the same way, including ineligible or deleted Requests, whose name is "unavailable": Requests the version calls that sharing never grants. Pass include_files: true to add each version's files with their individual SHA-256.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_app_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoApp slug; provide exactly one of slug or app_id
app_idNoApp UUID; provide exactly one of slug or app_id
include_filesNoInclude each version's files with their individual SHA-256; omitted keeps the listing to counts and bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: newest-first ordering, request alignment details, unavailable-name handling for ineligible or deleted Requests, and the include_files behavior. It does not disclose pagination, result limits, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is a dense run-on with deeply nested clauses and duplicated sorting language, making it hard to parse. It contains useful content but lacks front-loaded structure and clear separation between return fields and edge-case semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 return-value burden well by naming the fields, sorting rules, request alignment, unavailable entries, and optional files. It is nearly complete for a listing tool, though pagination or limits are unaddressed.

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 the schema already explains slug, app_id, and include_files. The description only repeats the include_files effect and does not add parameter syntax or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: list an app's immutable versions, newest first, with concrete returned fields. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as list_apps or describe_hosted_app_publishing.

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

Usage Guidelines2/5

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

The description implies usage by describing the returned version details but gives no explicit guidance on when to use this tool versus alternatives. It also omits prerequisites such as needing exactly one of slug or app_id, although the schema covers that.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources