Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

List archived assets

list_archived_assets
Read-onlyIdempotent

List original resources saved in this capture (images, fonts, video, audio and 3D models). Filter by source/path query or MIME prefix such as font/ or video/. Paginated metadata only; pass a resource path to get_capture_asset for its stored bytes.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items returned, clamped to 1..200. Default 50.
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.
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.
contentTypeNoCase-insensitive MIME-type prefix for archived resources, for example font/ or video/. Empty means all content types.
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
resultYesArchived original resource metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / contentType / description
      Added value: +"Case-insensitive MIME-type prefix for archived resources, for example font/ or video/. Empty means all content types."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items returned, clamped to 1..200. Default 50."
    • 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 / platform / description
      Added value: +"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."
    • addedInput schema / properties / product / description
      Added value: +"Product key, for example finance-ozon-ru"
    • 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: +{
+  "$defs": {
+    "resource": {
+      "additionalProperties": true,
+      "description": "Archived resource metadata",
+      "properties": {
+        "contentType": {
+          "description": "contentType",
+          "type": "string"
+        },
+        "hash": {
+          "description": "hash",
+          "type": "string"
+        },
+        "path": {
+          "description": "path",
+          "type": "string"
+        },
+        "sha256": {
+          "description": "sha256",
+          "type": "string"
+        },
+        "sizeBytes": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "source": {
+          "description": "source",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$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": "Archived original resource metadata",
+      "properties": {
+        "environment": {
+          "description": "environment",
+          "type": "string"
+        },
+        "hasMore": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "offset": {
+          "description": "offset",
+          "type": "integer"
+        },
+        "platform": {
+          "description": "platform",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "resources": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/resource"
+          },
+          "type": "array"
+        },
+        "total": {
+          "description": "total",
+          "type": "integer"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "platform",
+        "environment",
+        "version",
+        "total",
+        "offset",
+        "hasMore",
+        "resources"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds meaningful behavior beyond that: results are paginated metadata only and never the resource bytes, and there is a documented handoff path to get_capture_asset. It omits limits/clamping behavior, though the schema covers that.

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?

Two sentences with zero waste: the first gives scope and resource kinds, the second gives filtering plus pagination and the sibling handoff. Front-loaded and appropriately sized for an 8-parameter list tool.

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?

An output schema exists, so return values need not be described. The description covers scope, filtering, pagination, and the follow-up call, while required product/platform/version scoping is fully documented in the schema. Adequate, though a note on which fields query searches would close the last gap.

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 baseline is 3. The description earns an extra point by explaining what the filter parameters actually match — query against source/path and contentType as a MIME prefix with concrete examples (font/, video/) — which is genuinely needed since the schema's query text circularly refers to 'the fields documented by this tool'.

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?

States a specific verb+resource and enumerates the resource kinds (images, fonts, video, audio, 3D models) that constitute 'archived assets'. It also carves itself apart from get_capture_asset by declaring it returns metadata only. It does not, however, distinguish itself from the other list-family siblings (list_assets, list_product_assets, list_version_files), so sibling differentiation is only partial.

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?

Clear routing: use this tool for paginated metadata, then pass a resource path to get_capture_asset for stored bytes. It also tells the agent how to narrow results (query or MIME prefix). No explicit exclusion against the other list_* tools, which is the only gap.

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

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