Reconstruct

Get component animations

get_component_animations

Read-onlyIdempotent

Read captured motion and active CSS animation for one component ID. Paginated and optionally limited to a y range; excludes idle animation declarations.

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 component motion evidence

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 component motion evidence",
+      "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": "Animation record",
+            "properties": {
+              "animation": {
+                "anyOf": [
+                  {
+                    "description": "Text value",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "id": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "motion": {
+                "anyOf": [
+                  {
+                    "additionalProperties": true,
+                    "description": "Captured motion",
+                    "properties": {},
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "parent": {
+                "anyOf": [
+                  {
+                    "description": "Count or zero-based index",
+                    "type": "integer"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "rect": {
+                "anyOf": [
+                  {
+                    "$ref": "#/$defs/rect"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "parent",
+              "rect",
+              "motion",
+              "animation"
+            ],
+            "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.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds a genuinely useful behavioral fact not present in annotations or schema: idle animation declarations are excluded from results. It also flags pagination and optional y-range scoping, though those are largely mirrored in the schema.

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 the core action front-loaded and the exclusion clause last. Nothing is padded, though the second sentence packs three distinct facts (pagination, y-range, idle exclusion) into one clause chain.

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 the description need not explain return values, and the input schema fully documents the ten parameters. It is complete for calling the tool correctly; only the absence of sibling routing keeps it from being fully self-sufficient.

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 all ten parameters are already documented, including the non-obvious page/view/version/environment semantics. The description's 'paginated and optionally limited to a y range' only loosely gestures at limit/offset/yStart/yEnd and adds no new meaning, so the baseline 3 applies.

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 ('Read'), a specific resource ('captured motion and active CSS animation'), and scopes it to one component ID, which separates it from the page-level get_page_motion sibling. It stops short of naming that sibling or explicitly contrasting the two.

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 through 'for one component ID' and the y-range/pagination qualifiers, but never states when to choose this over get_page_motion, get_component_styles, or get_component_assets, nor any prerequisites beyond what the schema already encodes.

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?