Skip to main content
Glama

List version files

list_version_files
Read-onlyIdempotent

List stored paths for a product version, scoped to environment when supplied. Filter by prefix (for example platforms/macos/capture/pages or capture/pages) or substring query. Version metadata and content-addressed resources are shared across environments.

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": {
      "product": "<product>",
      "platform": "<platform>",
      "version": "<version>"
    },
    "name": "list_version_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items returned, clamped to 1..500. Default 200.
queryNoCase-insensitive search text. Empty means no filter; matches the fields documented by this tool.
offsetNoZero-based result offset for pagination. Negative values are treated as zero; default is 0.
prefixNoCapture-relative directory or exact filename prefix for list_version_files. Empty means all stored files.
productYesProduct key, for example finance-ozon-ru
versionYesExact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias.
platformYesPlatform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
environmentNoEnvironment ID from the selected backend platform type in list_platforms.options.platforms[].environments[].id (backend implementation). Omit only when the version has one captured environment. Use captured pairs from list_platforms/list_versions for actual availability.

Output Schema

NameRequiredDescriptionDefault
filesYesResult entries
totalYestotal
offsetYesoffset
productYesproduct
versionYesversion
platformYesplatform
environmentYesenvironment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Stored capture-relative filenames"
    • addedOutput schema / properties / environment
      Added value: +{
      +  "description": "environment",
      +  "type": "string"
      +}
    • addedOutput schema / properties / files
      Added value: +{
      +  "description": "Result entries",
      +  "items": {
      +    "description": "Text value",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "description": "offset",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / platform
      Added value: +{
      +  "description": "platform",
      +  "type": "string"
      +}
    • addedOutput schema / properties / product
      Added value: +{
      +  "description": "product",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Stored capture-relative filenames",
      -  "properties": {
      -    "environment": {
      -      "description": "environment",
      -      "type": "string"
      -    },
      -    "files": {
      -      "description": "Result entries",
      -      "items": {
      -        "description": "Text value",
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "offset": {
      -      "description": "offset",
      -      "type": "integer"
      -    },
      -    "platform": {
      -      "description": "platform",
      -      "type": "string"
      -    },
      -    "product": {
      -      "description": "product",
      -      "type": "string"
      -    },
      -    "total": {
      -      "description": "total",
      -      "type": "integer"
      -    },
      -    "version": {
      -      "description": "version",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "product",
      -    "platform",
      -    "environment",
      -    "version",
      -    "total",
      -    "offset",
      -    "files"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "total",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "version",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "product",
      +  "platform",
      +  "environment",
      +  "version",
      +  "total",
      +  "offset",
      +  "files"
      +]
  2. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items returned, clamped to 1..500. Default 200."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based result offset for pagination. Negative values are treated as zero; default is 0."
    • addedInput schema / properties / prefix / description
      Added value: +"Capture-relative directory or exact filename prefix for list_version_files. Empty means all stored files."
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive search text. Empty means no filter; matches the fields documented by this tool."
    • addedInput schema / properties / version / description
      Added value: +"Exact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "description": "Structured result. Existing text or image content remains available in content.",
      +  "properties": {
      +    "result": {
      +      "additionalProperties": true,
      +      "description": "Stored capture-relative filenames",
      +      "properties": {
      +        "environment": {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        "files": {
      +          "description": "Result entries",
      +          "items": {
      +            "description": "Text value",
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "offset": {
      +          "description": "offset",
      +          "type": "integer"
      +        },
      +        "platform": {
      +          "description": "platform",
      +          "type": "string"
      +        },
      +        "product": {
      +          "description": "product",
      +          "type": "string"
      +        },
      +        "total": {
      +          "description": "total",
      +          "type": "integer"
      +        },
      +        "version": {
      +          "description": "version",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "product",
      +        "platform",
      +        "environment",
      +        "version",
      +        "total",
      +        "offset",
      +        "files"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety bar is low, and the description adds real context beyond that: version metadata and content-addressed resources are shared across environments, which warns against over-claiming environment-specific results. It does not discuss result ordering or pagination behavior, but that is partly covered by the schema defaults.

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?

Three front-loaded sentences with no filler: purpose, filtering, then the cross-environment caveat in descending order of importance. Slightly dense and example-heavy, but every sentence carries information an agent needs.

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?

An output schema exists, so return-shape explanation is unnecessary, and all eight parameters are fully documented in the schema. The description supplies the remaining conceptual gap -- how path prefixes work and that version metadata/assets are shared across environments -- leaving nothing an agent needs in order to call this 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 100%, so the baseline would be 3, but the description earns above baseline by clarifying the two accepted prefix forms with concrete examples ('platforms/macos/capture/pages' vs 'capture/pages') and by explaining the environment scoping semantics that the schema only gestures at.

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 stored paths for a product version') and adds the scoping dimension ('scoped to environment when supplied') plus the two filter modes. That distinguishes it from list_versions (versions, not files) and from get_capture_asset (fetch contents, not list paths), though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

It tells the agent how to filter (prefix or substring query) and when environment may be omitted is covered only in the schema, not here. There is no explicit 'use X instead when...' routing to sibling listing or fetch tools, so the agent must infer when this tool is the right choice over list_versions, list_pages, or get_capture_asset.

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