Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get page outline

get_page_outline
Read-onlyIdempotent

Batch IR entry: list page sections plus regions (bundleTarget=true top-level). Call this first, then one get_section_bundle / get_page_bundles per region only — nested outline leaves are structure hints, not separate bundle targets.

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
resultYesMeasured page structure and recommended bundle regions

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: +{
+  "$defs": {
+    "outlineSection": {
+      "additionalProperties": true,
+      "description": "Measured outline section",
+      "properties": {
+        "bbox": {
+          "$ref": "#/$defs/rect"
+        },
+        "bundleTarget": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "childCount": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "id": {
+          "description": "Captured element ID",
+          "type": "integer"
+        },
+        "nested": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "parent": {
+          "anyOf": [
+            {
+              "description": "Parent element ID",
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "role": {
+          "description": "role",
+          "type": "string"
+        },
+        "tag": {
+          "description": "tag",
+          "type": "string"
+        },
+        "textPreview": {
+          "description": "textPreview",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "parent",
+        "role",
+        "tag",
+        "textPreview",
+        "bbox",
+        "childCount",
+        "nested",
+        "bundleTarget"
+      ],
+      "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": "Measured page structure and recommended bundle regions",
+      "properties": {
+        "guidance": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "regionCount": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "regions": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/outlineSection"
+          },
+          "type": "array"
+        },
+        "scrollHeight": {
+          "description": "Measured value",
+          "type": "number"
+        },
+        "sectionCount": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "sections": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/outlineSection"
+          },
+          "type": "array"
+        },
+        "truncated": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "viewportHeight": {
+          "description": "Measured value",
+          "type": "number"
+        }
+      },
+      "required": [
+        "viewportHeight",
+        "scrollHeight",
+        "truncated",
+        "guidance",
+        "sectionCount",
+        "regionCount",
+        "regions",
+        "sections"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuine workflow context — that nested outline leaves are structure hints rather than separate bundle targets — but does not clarify the 'bundleTarget=true top-level' filtering behavior or return shape in plain terms.

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 tight sentences with no filler, and the entry-point role is front-loaded. However, the density of unexplained jargon ('Batch IR entry', 'bundleTarget=true top-level') slightly undercuts readability.

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 no explanation, and annotations cover the safety profile. The description supplies the missing piece — the workflow relationship to bundle tools — making it adequate for this complexity level, with only the cryptic filter syntax left unexplained.

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 coverage is 100% and the parameter descriptions (page, view, version, environment) are already detailed and prescriptive. The description adds nothing about parameters, so the baseline of 3 applies since the schema carries the full semantic load.

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 concrete verb+resource ('list page sections plus regions') and positions itself as the entry point of a bundle workflow. It differentiates from siblings by naming get_section_bundle and get_page_bundles, though 'Batch IR entry' and 'bundleTarget=true top-level' are internal jargon that a fresh agent may not parse.

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?

Gives explicit ordering ('Call this first, then one get_section_bundle / get_page_bundles per region only') and names the alternative tools. It lacks an explicit when-not-to-use, but the sequencing constraint is clear enough to route the agent correctly.

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