Reconstruct

List pages

list_pages

Read-onlyIdempotent

Search and paginate captured pages in the selected environment. Optionally filter by platform type. views[] contains exact stored profile keys, platform type (null for legacy unclassified labels), and environment. Use these keys for page tools; desktop/mobile flags are legacy conveniences.

Input Schema

Name	Required	Description
`limit`	No	Maximum items returned, clamped to 1..100. Default 50.
`query`	No	Case-insensitive search text. Empty means no filter; matches the fields documented by this tool.
`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.
`platform`	No	Platform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
`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 captured pages in the selected environment

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 12, 2026

addedInput schema / properties / limit / description

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

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 / platform / description

Added value: +"Platform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately."

addedInput schema / properties / product / description

Added value: +"Product key, for example finance-ozon-ru"

addedInput schema / properties / query / description

Added value: +"Case-insensitive search text. Empty means no filter; matches the fields documented by this tool."

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": {
+    "pageEntry": {
+      "additionalProperties": true,
+      "description": "Captured page inventory entry",
+      "properties": {
+        "desktop": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "error": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "mobile": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "name": {
+          "description": "name",
+          "type": "string"
+        },
+        "url": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "views": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/view"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "name",
+        "views",
+        "url",
+        "error",
+        "desktop",
+        "mobile"
+      ],
+      "type": "object"
+    },
+    "view": {
+      "additionalProperties": true,
+      "description": "Stored view profile and captured platform/environment",
+      "properties": {
+        "environment": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "platform": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "view": {
+          "description": "Text value",
+          "type": "string"
+        }
+      },
+      "required": [
+        "view",
+        "platform",
+        "environment"
+      ],
+      "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 captured pages in the selected environment",
+      "properties": {
+        "environment": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "offset": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "pages": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/pageEntry"
+          },
+          "type": "array"
+        },
+        "total": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "environment",
+        "total",
+        "offset",
+        "pages"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: platform type may be null for legacy unclassified labels, environment is selected separately, and desktop/mobile flags are legacy conveniences rather than authoritative keys. It does not discuss pagination limits or result ordering, which keeps it at a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, so it is not padded. However, the second sentence pivots to describing views[] contents — return data already covered by the output schema — which muddles the focus of an input-side description and costs it structure points.

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 an output schema present and annotations covering the safety profile, the description only needs to explain scope and selection. It covers search, pagination, and optional platform filtering, and notes the legacy-key caveat. The main gap is that the query's matchable fields are deferred rather than named.

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 baseline is 3. The description reinforces that filtering is optional and warns that platform/environment keys are the exact stored values rather than the legacy desktop/mobile shortcuts, which is modest added meaning, but it provides no syntax or format detail the schema lacks.

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 specific verb+resource combination: 'Search and paginate captured pages in the selected environment.' That clearly separates it from the get_page_* siblings, which fetch a single page's detail. It does not explicitly name any sibling, so it falls short of 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 Guidelines3/5

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

Implies usage (paging through a captured environment's pages) and offers one routing hint, 'Use these keys for page tools,' but gives no explicit when-to-use/when-not guidance against list_versions, get_page_summary, or the other list_* tools. The condition for filtering by platform is stated only as 'optionally.'

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?