Skip to main content
Glama

Get component assets

get_component_assets
Read-onlyIdempotent

Read media references and geometry for one component ID. Paginated and optionally limited to a y range; resolve bytes via get_element_asset (URI/path by default).

Input Schema

NameRequiredDescriptionDefault
pageYesCaptured page key returned by list_pages or get_application_manifest, not a URL or filesystem path.
viewYesExact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
yEndNoNon-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.
limitNoMaximum items returned, clamped to 1..50. Default 20.
offsetNoZero-based result offset for pagination. Negative values are treated as zero; default is 0.
yStartNoNon-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.
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.
componentIdYesCaptured root element ID from get_page_components or get_page_outline. Must belong to the selected page, view and pinned version.
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
resultYesPaginated component media sources

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • 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 media sources",
      +      "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": "Media element",
      +            "properties": {
      +              "backgroundPosition": {
      +                "anyOf": [
      +                  {
      +                    "description": "Text value",
      +                    "type": "string"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "backgroundSize": {
      +                "anyOf": [
      +                  {
      +                    "description": "Text value",
      +                    "type": "string"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "id": {
      +                "anyOf": [
      +                  {
      +                    "description": "Count or zero-based index",
      +                    "type": "integer"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "kind": {
      +                "description": "Text value",
      +                "type": "string"
      +              },
      +              "rect": {
      +                "anyOf": [
      +                  {
      +                    "$ref": "#/$defs/rect"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "source": {
      +                "anyOf": [
      +                  {
      +                    "description": "Text value",
      +                    "type": "string"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              },
      +              "sourceLength": {
      +                "description": "Count or zero-based index",
      +                "type": "integer"
      +              },
      +              "tag": {
      +                "anyOf": [
      +                  {
      +                    "description": "Text value",
      +                    "type": "string"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ]
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "tag",
      +              "rect",
      +              "kind",
      +              "sourceLength",
      +              "source",
      +              "backgroundSize",
      +              "backgroundPosition"
      +            ],
      +            "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"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered. The description still adds real value by disclosing that the default response is a URI/path rather than bytes and must be resolved through get_element_asset, a trait present in neither schema nor annotations.

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 tight sentences with the primary purpose front-loaded, followed by scoping and the byte-resolution pointer. No filler and nothing redundant.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, scoping, pagination and byte resolution for a 10-parameter tool. A brief note on whether results include geometry alongside media would make it fully complete.

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 in the schema. The description only restates pagination and y-range scoping in passing and adds no syntax or format detail beyond that, 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?

The description opens with a specific verb and resource: 'Read media references and geometry for one component ID.' That clearly distinguishes it from byte-fetching siblings like get_component_image, though it does not explicitly contrast itself with the other get_component_* readers.

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 states the paginated/y-range scoping and routes the agent to get_element_asset to resolve actual bytes, which is genuine when-to-use guidance. It stops short of naming when not to use this tool or listing sibling alternatives.

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