Skip to main content
Glama

List archived assets

list_archived_assets
Read-onlyIdempotent

List original resources saved in this capture (images, fonts, video, audio and 3D models). Filter by source/path query or MIME prefix such as font/ or video/. Paginated metadata only; pass a resource path to get_capture_asset for its stored bytes.

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_archived_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items returned, clamped to 1..200. Default 50.
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.
contentTypeNoCase-insensitive MIME-type prefix for archived resources, for example font/ or video/. Empty means all content types.
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
offsetYesoffset
hasMoreYesWhether this condition holds
productYesproduct
versionYesversion
platformYesplatform
resourcesYesResult entries
environmentYesenvironment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 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: +"Archived original resource metadata"
    • addedOutput schema / properties / environment
      Added value: +{
      +  "description": "environment",
      +  "type": "string"
      +}
    • addedOutput schema / properties / hasMore
      Added value: +{
      +  "description": "Whether this condition holds",
      +  "type": "boolean"
      +}
    • 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"
      +}
    • addedOutput schema / properties / resources
      Added value: +{
      +  "description": "Result entries",
      +  "items": {
      +    "$ref": "#/$defs/resource"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Archived original resource metadata",
      -  "properties": {
      -    "environment": {
      -      "description": "environment",
      -      "type": "string"
      -    },
      -    "hasMore": {
      -      "description": "Whether this condition holds",
      -      "type": "boolean"
      -    },
      -    "offset": {
      -      "description": "offset",
      -      "type": "integer"
      -    },
      -    "platform": {
      -      "description": "platform",
      -      "type": "string"
      -    },
      -    "product": {
      -      "description": "product",
      -      "type": "string"
      -    },
      -    "resources": {
      -      "description": "Result entries",
      -      "items": {
      -        "$ref": "#/$defs/resource"
      -      },
      -      "type": "array"
      -    },
      -    "total": {
      -      "description": "total",
      -      "type": "integer"
      -    },
      -    "version": {
      -      "description": "version",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "product",
      -    "platform",
      -    "environment",
      -    "version",
      -    "total",
      -    "offset",
      -    "hasMore",
      -    "resources"
      -  ],
      -  "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",
      +  "hasMore",
      +  "resources"
      +]
  2. Changed8 schema fields changed
    • addedInput schema / properties / contentType / description
      Added value: +"Case-insensitive MIME-type prefix for archived resources, for example font/ or video/. Empty means all content types."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items returned, clamped to 1..200. 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": {
      +    "resource": {
      +      "additionalProperties": true,
      +      "description": "Archived resource metadata",
      +      "properties": {
      +        "contentType": {
      +          "description": "contentType",
      +          "type": "string"
      +        },
      +        "hash": {
      +          "description": "hash",
      +          "type": "string"
      +        },
      +        "path": {
      +          "description": "path",
      +          "type": "string"
      +        },
      +        "sha256": {
      +          "description": "sha256",
      +          "type": "string"
      +        },
      +        "sizeBytes": {
      +          "description": "Count or zero-based index",
      +          "type": "integer"
      +        },
      +        "source": {
      +          "description": "source",
      +          "type": "string"
      +        }
      +      },
      +      "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": "Archived original resource metadata",
      +      "properties": {
      +        "environment": {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        "hasMore": {
      +          "description": "Whether this condition holds",
      +          "type": "boolean"
      +        },
      +        "offset": {
      +          "description": "offset",
      +          "type": "integer"
      +        },
      +        "platform": {
      +          "description": "platform",
      +          "type": "string"
      +        },
      +        "product": {
      +          "description": "product",
      +          "type": "string"
      +        },
      +        "resources": {
      +          "description": "Result entries",
      +          "items": {
      +            "$ref": "#/$defs/resource"
      +          },
      +          "type": "array"
      +        },
      +        "total": {
      +          "description": "total",
      +          "type": "integer"
      +        },
      +        "version": {
      +          "description": "version",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "product",
      +        "platform",
      +        "environment",
      +        "version",
      +        "total",
      +        "offset",
      +        "hasMore",
      +        "resources"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description still adds real value beyond them: results are metadata only (no bytes), results are paginated, and filtering is narrowing/case-insensitive. It doesn't mention ordering of results or what happens at the limit ceiling, but the key behavioral contract is stated.

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?

Three short sentences with no filler: scope first, filtering second, handoff third. The most decision-relevant constraint (metadata only, bytes live in get_capture_asset) is placed last but is short enough not to be buried.

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?

For an 8-parameter, read-only list tool with an output schema and full annotation coverage, the description supplies the essentials: what is listed, how to narrow, and where to go for bytes. The required product/platform/version/environment selection flow is not mentioned, but the schema descriptions for those parameters already carry it and an output schema exists, so the gap is minor.

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 parameter is already documented in the schema, and the description's MIME-prefix examples ('font/ or video/') largely restate contentType's own description. Its one marginal addition is clarifying that `query` matches source/path, i.e. a substring search over resource locations rather than content. Baseline 3 applies since the schema does the heavy lifting.

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?

The description opens with a specific verb and resource plus the concrete content scope: 'List original resources saved in this capture (images, fonts, video, audio and 3D models).' It clearly separates itself from get_capture_asset, though it never distinguishes this tool from the sibling list_assets or list_product_assets, which an agent would also have to choose between.

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?

It explicitly states the selection rule against get_capture_asset: 'Paginated metadata only; pass a resource path to get_capture_asset for its stored bytes.' It also explains the two filtering modes (query text vs MIME prefix), but gives no guidance on when to use this over list_assets / list_product_assets.

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