Reconstruct

Get element asset

get_element_asset

Read-onlyIdempotent

Resolve one captured element asset. Returns path/URI, hash, MIME and byte size by default. Download or copy it outside model context. includeContent=true requests inline bytes within the configured raw-byte limit; oversized assets remain references.

Input Schema

Name	Required	Description
`page`	Yes	Captured page key returned by list_pages or get_application_manifest, not a URL or filesystem path.
`view`	Yes	Exact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
`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.
`elementId`	Yes	Zero-based captured element ID from find_elements or get_elements. Must belong to the selected page, view and pinned version.
`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.
`includeContent`	No	Include asset content only when within the server inline-size limit. Default false returns references without embedding bytes.

Output Schema

Name	Required	Description	Default
`result`	Yes	Chosen element media reference

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 12, 2026

addedInput schema / properties / elementId / description

Added value: +"Zero-based captured element ID from find_elements or get_elements. Must belong to the selected page, view and pinned version."

addedInput schema / properties / includeContent / description

Added value: +"Include asset content only when within the server inline-size limit. Default false returns references without embedding bytes."

addedInput schema / properties / page / description

Added value: +"Captured page key returned by list_pages or get_application_manifest, not a URL or filesystem path."

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"
+    },
+    "rect": {
+      "additionalProperties": true,
+      "description": "Captured CSS-pixel rectangle",
+      "properties": {
+        "height": {
+          "description": "height",
+          "type": "number"
+        },
+        "width": {
+          "description": "width",
+          "type": "number"
+        },
+        "x": {
+          "description": "x",
+          "type": "number"
+        },
+        "y": {
+          "description": "y",
+          "type": "number"
+        }
+      },
+      "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": "Chosen element media reference",
+      "properties": {
+        "asset": {
+          "$ref": "#/$defs/asset"
+        },
+        "id": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "rect": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/rect"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "tag": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "tag",
+        "rect",
+        "asset"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond the annotations: the default return shape (path/URI, hash, MIME, byte size) and the fact that oversized assets stay as references even when includeContent=true.

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?

Four compact sentences, front-loaded with the core action and default return shape before the optional includeContent detail. No filler, and each 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 an output schema present, the description needn't detail returns, yet it summarizes them usefully, and it covers the one non-obvious parameter (includeContent). Complete enough to call the tool correctly; only sibling disambiguation is thin.

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 and the schema does the heavy lifting. The description still adds value by explaining includeContent's raw-byte-limit and oversized-fallback semantics, which the schema only states more tersely.

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 ('Resolve') and resource ('one captured element asset'), with a clear single-item scope. It does not, however, name or differentiate itself from close siblings like get_capture_asset or get_component_assets, so an agent must infer the distinction.

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?

Gives one useful directive: 'Download or copy it outside model context,' and conditions includeContent=true on wanting inline bytes. But there is no explicit when-to-use-this-vs-sibling guidance among the many asset/get_* tools, 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?