Skip to main content
Glama

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. Inline fonts are excluded (use get_fonts); inline data URLs longer than 2048 characters are abbreviated to data:;abbreviated;bytes=;sha256= (read the bytes with get_element_asset). Prefer this over per-page list_assets for product-wide inventory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>",
      "platform": "<platform>",
      "version": "<version>"
    },
    "name": "list_product_assets"
  }
}

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
totalYestotal
assetsYesResult entries
offsetYesoffset
productYesproduct
versionYesversion
platformYesplatform
environmentYesenvironment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Product-wide original media inventory"
    • addedOutput schema / properties / assets
      Added value: +{
      +  "description": "Result entries",
      +  "items": {
      +    "description": "Original URL or inline SVG data URL",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / environment
      Added value: +{
      +  "description": "environment",
      +  "type": "string"
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "description": "offset",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / platform
      Added value: +{
      +  "description": "platform",
      +  "type": "string"
      +}
    • addedOutput schema / properties / product
      Added value: +{
      +  "description": "product",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "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"
      -}
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "total",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "version",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "product",
      +  "platform",
      +  "environment",
      +  "version",
      +  "total",
      +  "offset",
      +  "assets"
      +]
  2. 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"
      +}
  3. First observed

TDQS

A4.4/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), yet the description still adds real behavioral detail: the data source (assets.json), the fact that inline fonts are omitted, and a precise truncation contract (data URLs over 2048 chars become data:<mime>;abbreviated;bytes=<n>;sha256=<hex>). It goes further by naming the recovery path, get_element_asset, for reading the truncated bytes — behavior an agent would otherwise discover only by surprise. It stops short of describing ordering of results, so not 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.

Conciseness4/5

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

Three tight sentences with the core purpose front-loaded, then exclusions, then the truncation contract, then the sibling preference. Dense but every clause carries information; the mid-sentence abbreviation template is unavoidably verbose and slightly disrupts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists and the input schema is fully documented, the description supplies exactly the missing pieces: scope, source file, excluded asset types, truncation semantics, and the alternative tools for both fonts and per-page listing. An agent has everything needed to call it correctly and interpret abbreviated values.

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 product, platform, version, environment, query, limit and offset are all already documented in the schema, including provenance (list_platforms, list_versions) and clamping rules. The description adds only the indirect hints "filtered" and "product-wide" and does not clarify query match fields or pagination behavior beyond what the schema states, so the baseline of 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 (media assets) and precise scope (a product version on a platform, sourced from assets.json), then enumerates what counts: linked images and inline SVG data URLs. It explicitly names the sibling it supersedes (per-page list_assets) and the sibling that owns the excluded content (get_fonts), so an agent can choose without opening a 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?

Gives an explicit routing rule: "Prefer this over per-page list_assets for product-wide inventory," plus an exclusion rule for inline fonts pointing at get_fonts. Both when-to-use and when-not-to-use are stated with the correct alternative named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources