Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get page artifacts

get_page_artifacts
Read-onlyIdempotent

List stored media for one page/view: viewport and full-page screenshots, section tiles, scroll and interaction recordings. Returns relative paths and MIME types plus capture-limit metadata. Retrieve a chosen file with get_capture_asset; absent recordings are not invented.

Input Schema

NameRequiredDescriptionDefault
pageYesCaptured page key returned by list_pages or get_application_manifest, not a URL or filesystem path.
viewYesExact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
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.
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
resultYesStored media and capture limitations for a page/view

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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: +{
+  "$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 media and capture limitations for a page/view",
+      "properties": {
+        "artifacts": {
+          "description": "Result entries",
+          "items": {
+            "additionalProperties": true,
+            "description": "Stored media file",
+            "properties": {
+              "contentType": {
+                "description": "contentType",
+                "type": "string"
+              },
+              "path": {
+                "description": "path",
+                "type": "string"
+              }
+            },
+            "required": [
+              "path",
+              "contentType"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "captureLimited": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "environment": {
+          "description": "environment",
+          "type": "string"
+        },
+        "limitations": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "description": "Capture-limit metadata",
+              "properties": {},
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "page": {
+          "description": "page",
+          "type": "string"
+        },
+        "platform": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        },
+        "view": {
+          "description": "view",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "environment",
+        "version",
+        "page",
+        "view",
+        "platform",
+        "captureLimited",
+        "limitations",
+        "artifacts"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real context beyond that: relative (not absolute) paths, MIME types, capture-limit metadata, and the notable guarantee that absent recordings are not fabricated — a behavioral claim the annotations do not 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: contents first, then return shape, then the retrieval handoff and the no-fabrication caveat. Every clause earns its place and the most important information is front-loaded.

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 to describe return values and annotations cover the safety profile, so the description need not carry those burdens. It supplies purpose, scope, artifact classes, return shape, downstream routing and a behavioral caveat — everything an agent needs to select and call it correctly.

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 description coverage is 100% and the schema already documents page, view, version and environment with strong semantics (exact keys, no URL/path, no 'latest' alias). The description only echoes the 'one page/view' scoping, adding nothing the schema does not already say, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and resource (stored media for one page/view) and enumerates the artifact classes it covers: viewport/full-page screenshots, section tiles, scroll and interaction recordings. This distinguishes it clearly from single-asset siblings like get_page_image or get_capture_image and from bundle-style siblings.

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?

It routes the agent explicitly to the follow-up step ("Retrieve a chosen file with get_capture_asset"), which is useful workflow guidance. It stops short of naming when NOT to use this tool vs alternatives like get_page_bundles or list_version_files, so it is clear context without exclusions.

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