Reconstruct

Get capture asset

get_capture_asset

Read-onlyIdempotent

Materialize an archived resource or stored screenshot/MP4/WebM by relative path. Returns path, URI, hash, MIME and size without embedding bytes. Discover resources with list_archived_assets/get_fonts and recordings with get_page_artifacts. Full page JSON is excluded.

Input Schema

Name	Required	Description
`path`	Yes	Capture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed.
`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	Archived media materialization

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 12, 2026

addedInput schema / properties / path / description

Added value: +"Capture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed."

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 / 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": {
+    "asset": {
+      "additionalProperties": true,
+      "description": "Materialized or original media reference; inline content is optional",
+      "properties": {
+        "content": {
+          "description": "Inline base64 bytes or reference when requested and within size limit",
+          "type": "string"
+        },
+        "hash": {
+          "description": "hash",
+          "type": "string"
+        },
+        "kind": {
+          "description": "kind",
+          "type": "string"
+        },
+        "mime": {
+          "description": "mime",
+          "type": "string"
+        },
+        "path": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "size": {
+          "description": "Byte count or source-reference length",
+          "type": "integer"
+        },
+        "uri": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "kind",
+        "mime",
+        "size",
+        "hash",
+        "path",
+        "uri"
+      ],
+      "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 media materialization",
+      "properties": {
+        "asset": {
+          "$ref": "#/$defs/asset"
+        },
+        "environment": {
+          "description": "environment",
+          "type": "string"
+        },
+        "path": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "platform": {
+          "description": "platform",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "platform",
+        "environment",
+        "version",
+        "path",
+        "asset"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A4/5.0

Behavior4/5

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

With readOnlyHint/idempotentHint/destructiveHint already declared, the description still adds genuinely useful context: the return shape (path, URI, hash, MIME, size) and the key behavior that bytes are not embedded and page JSON is excluded. This goes beyond the safety profile the annotations carry.

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 tight sentences, front-loaded with the core action and return summary, then discovery routing and an exclusion. No filler.

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?

Output schema exists so return values needn't be explained (though the description usefully previews them), and annotations cover the safety profile. The description adds the exclusion and discovery pointers, making it largely complete, with only minor gaps around pagination/size limits.

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 coverage is 100%, so the schema already documents all five parameters, including path constraints and the environment default. The description only echoes 'by relative path,' adding little beyond the schema, so the baseline 3 applies.

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 (materialize) and resource types (archived resource, screenshot/MP4/WebM) retrieved by relative path. It names discovery siblings (list_archived_assets, get_fonts, get_page_artifacts), which aids differentiation, though it does not clearly separate itself from other retrieval siblings like get_page_image or get_element_asset.

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?

Gives workflow guidance by pointing to the discovery tools that produce the path (list_archived_assets/get_fonts for resources, get_page_artifacts for recordings) and notes page JSON is excluded. No explicit when-not or limits on the other asset-getter siblings, so it stops short of full alternative coverage.

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?