Reconstruct

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.

Input Schema

Name	Required	Description
`limit`	No	Maximum items returned, clamped to 1..500. Default 200.
`query`	No	Case-insensitive search text. Empty means no filter; matches the fields documented by this tool.
`offset`	No	Zero-based result offset for pagination. Negative values are treated as zero; default is 0.
`prefix`	No	Capture-relative directory or exact filename prefix for list_version_files. Empty means all stored files.
`product`	Yes	Product key, for example finance-ozon-ru
`version`	Yes	Exact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias.
`platform`	Yes	Platform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
`environment`	No	Environment 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

Name	Required	Description	Default
`result`	Yes	Stored capture-relative filenames

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 12, 2026

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"
+}

First observedOct 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: environment-scoped path listing and the fact that version metadata and content-addressed resources are shared across environments, which affects how results should be interpreted.

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 short clauses with zero waste, and the scope statement is front-loaded before the filtering details. Every sentence carries distinct information.

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 8 params, 3 required, full schema coverage and an output schema, the description only needs to cover purpose, scoping and filtering semantics, which it does. Pagination/limit behavior is left entirely to the schema, which is acceptable but slightly thin for a list operation.

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 description coverage is 100%, so the baseline is 3. The description earns extra credit by giving concrete prefix values ('platforms/macos/capture/pages or capture/pages') and clarifying the substring-query mode, adding meaning the schema's terse parameter docs do not supply.

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 names a specific verb and resource: 'List stored paths for a product version'. This clearly distinguishes it from list_versions (which enumerates versions) and the various get_* content tools, though no sibling is named explicitly and the agent must infer the boundary from resource wording alone.

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 supplies usable context for the two filtering modes (prefix vs substring query) with concrete path examples, and notes that environment scoping applies 'when supplied'. However, it never states when to choose this tool over alternatives like list_pages or list_assets, nor any when-not condition, leaving routing to inference.

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

All Reconstruct tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?