Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

List product assets

list_product_assets
Read-onlyIdempotent

List filtered media assets for a product version on a platform (from assets.json): linked images and inline SVG data URLs. Prefer this over per-page list_assets for product-wide inventory.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items returned, clamped to 1..300. Default 100.
queryNoCase-insensitive search text. Empty means no filter; matches the fields documented by this tool.
offsetNoZero-based result offset for pagination. Negative values are treated as zero; default is 0.
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.
platformYesPlatform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
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
resultYesProduct-wide original media inventory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items returned, clamped to 1..300. Default 100."
    • 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 / 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: +{
+  "$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": "Product-wide original media inventory",
+      "properties": {
+        "assets": {
+          "description": "Result entries",
+          "items": {
+            "description": "Original URL or inline SVG data URL",
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "environment": {
+          "description": "environment",
+          "type": "string"
+        },
+        "offset": {
+          "description": "offset",
+          "type": "integer"
+        },
+        "platform": {
+          "description": "platform",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "total": {
+          "description": "total",
+          "type": "integer"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "platform",
+        "environment",
+        "version",
+        "total",
+        "offset",
+        "assets"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new context: the backing source (assets.json) and the returned content types (linked images and inline SVG data URLs), which the annotations cannot convey.

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?

Two sentences, zero filler, with the identifying scope front-loaded ahead of the sibling-routing advice. Every clause earns its place.

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?

Output schema exists so return shape need not be explained, and parameters are fully covered by the schema. The description supplies the essentials for selection; only deeper filtering semantics or auth/prerequisite notes are absent.

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 every one of the 7 parameters including limit/offset/query/environment is already documented in the schema. The description only implies filtering via the word 'filtered' and adds no syntax or format detail. 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 (List), resource (product assets), and scope (filtered media assets for a product version on a platform), and names the sibling it supersedes (list_assets). An agent can distinguish it from list_assets and get_capture_asset 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?

'Prefer this over per-page list_assets for product-wide inventory' names the alternative and the condition that selects this tool. It stops short of explicit when-not guidance, but the routing intent is unambiguous.

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