Reconstruct

Get page components

get_page_components

Read-onlyIdempotent

List visual component candidates in a bounded y region (exact follow-up). Prefer get_page_outline → one bundle per outline region (or get_page_bundles) to avoid exploratory spam across many y bands or micro-sections.

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.
`yEnd`	No	Non-negative vertical end coordinate in captured CSS pixels; default 0 selects one viewport from yStart. A vertical fragment may span at most two viewport heights.
`limit`	No	Maximum items returned, clamped to 1..50. Default 20.
`offset`	No	Zero-based result offset for pagination. Negative values are treated as zero; default is 0.
`yStart`	No	Non-negative vertical start coordinate in captured CSS pixels; default 0. When both bounds are 0, component layers use the component bounds and page layers use the first viewport.
`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.
`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	Paginated candidate components in a vertical fragment

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 12, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum items returned, clamped to 1..50. Default 20."

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 / 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."

addedInput schema / properties / yEnd / description

Added value: +"Non-negative vertical end coordinate in captured CSS pixels; default 0 selects one viewport from yStart. A vertical fragment may span at most two viewport heights."

addedInput schema / properties / yStart / description

Added value: +"Non-negative vertical start coordinate in captured CSS pixels; default 0. When both bounds are 0, component layers use the component bounds and page layers use the first viewport."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "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": "Paginated candidate components in a vertical fragment",
+      "properties": {
+        "componentId": {
+          "anyOf": [
+            {
+              "description": "Count or zero-based index",
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "hasMore": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "items": {
+          "description": "Result entries",
+          "items": {
+            "additionalProperties": true,
+            "description": "Candidate component",
+            "properties": {
+              "childCount": {
+                "description": "Count or zero-based index",
+                "type": "integer"
+              },
+              "id": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "label": {
+                "description": "Text value",
+                "type": "string"
+              },
+              "parent": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "rect": {
+                "anyOf": [
+                  {
+                    "$ref": "#/$defs/rect"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "role": {
+                "description": "Text value",
+                "type": "string"
+              },
+              "tag": {
+                "anyOf": [
+                  {
+                    "description": "Text value",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "parent",
+              "tag",
+              "rect",
+              "role",
+              "childCount",
+              "label"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "layer": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "offset": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "total": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "truncated": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "yEnd": {
+          "description": "Measured value",
+          "type": "number"
+        },
+        "yStart": {
+          "description": "Measured value",
+          "type": "number"
+        }
+      },
+      "required": [
+        "layer",
+        "componentId",
+        "yStart",
+        "yEnd",
+        "truncated",
+        "total",
+        "offset",
+        "hasMore",
+        "items"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real but modest context: this is an 'exact follow-up' query and over-calling across y bands produces 'exploratory spam.' It does not address auth, rate limits, or response characteristics, so it is adequate rather than rich.

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?

Two sentences, front-loaded with the core action followed by the routing guidance; no filler. The parenthetical '(exact follow-up)' is slightly cryptic and could be clearer, which keeps it from a 5.

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 explained, and annotations cover safety. For a 9-param, region-bounded listing tool the description supplies enough routing and scope context to call it correctly, though it omits page/view/version pairing nuance that the schema carries.

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%, so the schema already documents all 9 parameters (yStart/yEnd, limit, offset, page, view, product, version, environment) in detail. The description only gestures at the 'bounded y region' that yStart/yEnd encode, adding no syntax or semantics beyond the schema.

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?

Specific verb ('List') plus resource ('visual component candidates') and a scoping constraint ('in a bounded y region'), and it names two sibling tools (get_page_outline, get_page_bundles) as the preferred route. It is clear what the tool does, though it does not distinguish itself from the similarly named sibling list_component_candidates, keeping it just below a 5.

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?

Explicitly says to 'Prefer get_page_outline → one bundle per outline region (or get_page_bundles)' and gives the rationale ('to avoid exploratory spam across many y bands or micro-sections'). This is clear when-to-use and alternative-naming guidance; it lacks an explicit when-not/precondition statement, so not a full 5.

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?