Reconstruct

Get component tree

get_component_tree

Read-onlyIdempotent

Read a component's compact parent/child skeleton by element ID and depth, without text, CSS, animation, or asset data.

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.
`depth`	No	Maximum descendant depth from the root component, clamped to 0..4. Default 2; depth 0 returns only the root.
`limit`	No	Maximum items returned, clamped to 1..50. Default 40.
`offset`	No	Zero-based result offset for pagination. Negative values are treated as zero; default is 0.
`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.
`componentId`	Yes	Captured root element ID from get_page_components or get_page_outline. 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.

Output Schema

Name	Required	Description	Default
`result`	Yes	Paginated component ancestry and descendants

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 12, 2026

addedInput schema / properties / componentId / description

Added value: +"Captured root element ID from get_page_components or get_page_outline. Must belong to the selected page, view and pinned version."

addedInput schema / properties / depth / description

Added value: +"Maximum descendant depth from the root component, clamped to 0..4. Default 2; depth 0 returns only the root."

addedInput schema / properties / limit / description

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

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

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 component ancestry and descendants",
+      "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": "Tree node",
+            "properties": {
+              "childCount": {
+                "description": "Count or zero-based index",
+                "type": "integer"
+              },
+              "depth": {
+                "description": "Count or zero-based index",
+                "type": "integer"
+              },
+              "id": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "layoutMode": {
+                "anyOf": [
+                  {
+                    "description": "Text value",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "parent": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "rect": {
+                "anyOf": [
+                  {
+                    "$ref": "#/$defs/rect"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "tag": {
+                "anyOf": [
+                  {
+                    "description": "Text value",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "parent",
+              "tag",
+              "rect",
+              "depth",
+              "layoutMode",
+              "childCount"
+            ],
+            "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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so safety is covered. The description adds real behavioral value by characterizing the response as a 'compact parent/child skeleton' and enumerating what is deliberately omitted, letting an agent predict payload weight versus the heavier asset/style siblings.

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?

A single sentence that front-loads the action and resource, then qualifies scope with the exclusion list. No filler, no repetition of schema facts.

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 a rich schema (9 params, 5 required, 100% coverage), an output schema, and full annotations, the description covers what an agent needs to invoke it correctly. Only a brief note on pagination or result shape would improve it, and the output schema already handles returns.

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 documents defaults, clamps (0..4, 1..50), and pagination semantics in detail. The description only echoes 'element ID and depth', adding no syntax or constraint beyond the schema, so the baseline of 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 (Read) and resource (component's parent/child skeleton) and immediately scopes the payload by element ID and depth. The exclusion clause (no text, CSS, animation, asset data) separates it cleanly from siblings like get_component_text, get_component_styles, and get_component_assets without opening any schema.

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?

The 'without text, CSS, animation, or asset data' exclusion gives clear context that routes the agent toward the specialized sibling tools when those payloads are needed. However, it never explicitly names an alternative or states a when-not condition, so the routing is implied rather than spelled out.

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?