Skip to main content
Glama

Get capture image

get_capture_image
Read-onlyIdempotent

Read one allowlisted WebP from a product version by relative path (for example before.webp, capture/pages/home/desktop/viewport.webp). Only .webp paths present in storage are readable.

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>",
      "path": "<path>"
    },
    "name": "get_capture_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesCapture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed.
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
mimeTypeYesMIME type of the returned image
contentIndexYesZero-based index of the ImageContentBlock

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / $defs
      Removed value: -{
      -  "image": {
      -    "additionalProperties": false,
      -    "description": "Metadata for the image in content[contentIndex]; image bytes are not duplicated here",
      -    "properties": {
      -      "contentIndex": {
      -        "const": 0,
      -        "description": "Zero-based index of the ImageContentBlock",
      -        "type": "integer"
      -      },
      -      "mimeType": {
      -        "description": "MIME type of the returned image",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "mimeType",
      -      "contentIndex"
      -    ],
      -    "type": "object"
      -  }
      -}
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Metadata for the image in content[contentIndex]; image bytes are not duplicated here"
    • addedOutput schema / properties / contentIndex
      Added value: +{
      +  "const": 0,
      +  "description": "Zero-based index of the ImageContentBlock",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / mimeType
      Added value: +{
      +  "description": "MIME type of the returned image",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$ref": "#/$defs/image"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "mimeType",
      +  "contentIndex"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / path / description
      Added value: +"Capture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed."
    • 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": {
      +    "image": {
      +      "additionalProperties": false,
      +      "description": "Metadata for the image in content[contentIndex]; image bytes are not duplicated here",
      +      "properties": {
      +        "contentIndex": {
      +          "const": 0,
      +          "description": "Zero-based index of the ImageContentBlock",
      +          "type": "integer"
      +        },
      +        "mimeType": {
      +          "description": "MIME type of the returned image",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "mimeType",
      +        "contentIndex"
      +      ],
      +      "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": {
      +      "$ref": "#/$defs/image"
      +    }
      +  },
      +  "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 declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuine behavioral context by disclosing an access restriction ('only .webp paths present in storage are readable'), which tells the agent this can fail on non-allowlisted paths. It stops short of describing error shape or size limits, but the allowlist note is real added value.

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?

A single front-loaded sentence with the resource and the access constraint stated first, and the inline path examples are short enough to earn their place as format illustration. Nothing is padded, though the sentence packs two ideas that could be split for skimmability.

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 a read-only image fetch with full schema coverage, an output schema, and safety annotations, the description covers what it must: what is read, the path format, and the allowlist limit. The only real gap is disambiguation from the crowded set of sibling image tools.

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 five parameters (including environment) are already documented with sourcing hints. The description's contributions beyond the schema are the sample path strings and the 'from a product version' framing, which are marginal, so 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?

States a specific verb and resource ('Read one allowlisted WebP from a product version by relative path') with concrete path examples, so the operation is unambiguous. It does not, however, distinguish itself from the many sibling image tools (get_capture_asset, get_page_image, get_click_image, get_stage_image), leaving the agent to infer that this one addresses archived capture files rather than live assets.

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?

The description implies usage via the allowlist constraint and the requirement that the path be capture-relative, but it never states when to choose this over get_capture_asset or the other image siblings, nor any prerequisite flow ('call list_version_files first'). 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