Reconstruct

Get component text

get_component_text

Read-onlyIdempotent

Exact follow-up: visible own text, line breaks, IDs, parents, and rectangles for one component ID. Prefer get_section_bundle text/texts first; call this when the bundle marks textTruncated or you need uncapped runs/lines. Paginated and optionally limited to a y range; no CSS or asset payloads.

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.
`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 own text of captured component descendants

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 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 / 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 own text of captured component 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": "Text element",
+            "properties": {
+              "id": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "lines": {
+                "anyOf": [
+                  {
+                    "description": "Result entries",
+                    "items": {
+                      "description": "Text value",
+                      "type": "string"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "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"
+                  }
+                ]
+              },
+              "text": {
+                "description": "Text value",
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "parent",
+              "tag",
+              "rect",
+              "text",
+              "lines"
+            ],
+            "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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description still adds real behavioral value: it discloses pagination, an optional y-range restriction, and a scope boundary ('no CSS or asset payloads'), which tells the agent what this call will not return. It does not mention rate limits or auth requirements, so it stops short of a 5.

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 dense sentences: what is returned, when to use it instead of the bundle, and the operational constraints. Front-loaded with the core deliverable and free of 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?

An output schema exists, so return-value explanation is not required, and the description covers routing, pagination and scope. Prerequisite pinning (version/page/view consistency) is handled entirely by schema descriptions, leaving little the agent still needs to infer, though a note on truncation behaviour at the limit cap would round it out.

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 page, view, version, componentId, yStart/yEnd, limit and offset are all already documented in the schema. The description only alludes to pagination and the y range without adding syntax or defaults beyond what the schema provides, 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 and resource ('visible own text, line breaks, IDs, parents, and rectangles for one component ID') and names the exact scope of what comes back. It also distinguishes itself from the sibling get_section_bundle, so an agent can choose between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: 'Prefer get_section_bundle text/texts first; call this when the bundle marks textTruncated or you need uncapped runs/lines.' This gives both the preferred alternative and the precise triggering condition, which is exactly what usage guidance should do.

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?