Skip to main content
Glama

Get element asset

get_element_asset
Read-onlyIdempotent

Resolve one captured element asset. Returns path/URI, hash, MIME and byte size by default. Download or copy it outside model context. includeContent=true requests inline bytes within the configured raw-byte limit; oversized assets remain references.

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>",
      "version": "<version>",
      "page": "<page>",
      "view": "<view>",
      "elementId": "<elementId>"
    },
    "name": "get_element_asset"
  }
}

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.
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.
elementIdYesZero-based captured element ID from find_elements or get_elements. 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.
includeContentNoInclude asset content only when within the server inline-size limit. Default false returns references without embedding bytes.

Output Schema

NameRequiredDescriptionDefault
idYesCount or zero-based index
tagYes
rectYes
assetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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: +"Chosen element media reference"
    • addedOutput schema / properties / asset
      Added value: +{
      +  "$ref": "#/$defs/asset"
      +}
    • addedOutput schema / properties / id
      Added value: +{
      +  "description": "Count or zero-based index",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / rect
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/rect"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Chosen element media reference",
      -  "properties": {
      -    "asset": {
      -      "$ref": "#/$defs/asset"
      -    },
      -    "id": {
      -      "description": "Count or zero-based index",
      -      "type": "integer"
      -    },
      -    "rect": {
      -      "anyOf": [
      -        {
      -          "$ref": "#/$defs/rect"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "tag": {
      -      "anyOf": [
      -        {
      -          "description": "Text value",
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    }
      -  },
      -  "required": [
      -    "id",
      -    "tag",
      -    "rect",
      -    "asset"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / tag
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Text value",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "id",
      +  "tag",
      +  "rect",
      +  "asset"
      +]
  2. Changed6 schema fields changed
    • addedInput schema / properties / elementId / description
      Added value: +"Zero-based captured element ID from find_elements or get_elements. Must belong to the selected page, view and pinned version."
    • addedInput schema / properties / includeContent / description
      Added value: +"Include asset content only when within the server inline-size limit. Default false returns references without embedding bytes."
    • 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "asset": {
      +      "additionalProperties": true,
      +      "description": "Materialized or original media reference; inline content is optional",
      +      "properties": {
      +        "content": {
      +          "description": "Inline base64 bytes or reference when requested and within size limit",
      +          "type": "string"
      +        },
      +        "hash": {
      +          "description": "hash",
      +          "type": "string"
      +        },
      +        "kind": {
      +          "description": "kind",
      +          "type": "string"
      +        },
      +        "mime": {
      +          "description": "mime",
      +          "type": "string"
      +        },
      +        "path": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "size": {
      +          "description": "Byte count or source-reference length",
      +          "type": "integer"
      +        },
      +        "uri": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "mime",
      +        "size",
      +        "hash",
      +        "path",
      +        "uri"
      +      ],
      +      "type": "object"
      +    },
      +    "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": "Chosen element media reference",
      +      "properties": {
      +        "asset": {
      +          "$ref": "#/$defs/asset"
      +        },
      +        "id": {
      +          "description": "Count or zero-based index",
      +          "type": "integer"
      +        },
      +        "rect": {
      +          "anyOf": [
      +            {
      +              "$ref": "#/$defs/rect"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "tag": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "tag",
      +        "rect",
      +        "asset"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered; the description earns credit for adding behavior annotations cannot express — that the default is metadata-only, that inlining is bounded by a configured raw-byte limit, and that oversized assets silently degrade to references instead of failing. That last point is exactly the kind of surprise an agent needs warned about. It stops short of 5 because auth/environment requirements and failure modes are left to 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?

Four short sentences, front-loaded with the return contract before the includeContent caveat. Nothing is padding, though the final clause about oversized assets restates the includeContent schema note closely enough to be near-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?

With an output schema present, the description needn't explain return shapes, and it doesn't over-invest there. Required-parameter sourcing (page/view/version/elementId lineage) is fully handled in the schema, so what remains — the default payload and the inline-bytes boundary — is adequately covered for a read-only resolver.

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 seven parameters are already documented, and the baseline of 3 applies. The description reinforces includeContent's consequence (oversized assets remain references) but adds no format, unit, or sourcing detail beyond what the schema properties already state.

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?

Description opens with a specific verb+resource ("Resolve one captured element asset") and immediately names the default return payload (path/URI, hash, MIME, byte size), so the agent knows exactly what comes back. It distinguishes itself from list_assets/get_capture_asset only implicitly — the word "element" scopes it, but no sibling is named, so an agent choosing between get_element_asset, get_capture_asset and get_component_assets gets no explicit tiebreaker.

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?

"Download or copy it outside model context" and "includeContent=true requests inline bytes" give a usable decision rule for the inline-vs-reference choice. Beyond that there is no when-to-use framing relative to the many sibling asset tools, and no prerequisites or exclusions stated, so guidance is implied rather than explicit.

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