Skip to main content
Glama

Get page image

get_page_image
Read-onlyIdempotent

Return a captured viewport WebP for an exact stored page profile key from list_pages, in the selected environment.

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

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.
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. Changed4 schema fields changed
    • 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": {
      +    "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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds the output format (WebP) and the constraint that the key must be an exact stored profile, but says nothing about availability, missing captures, or what the selected environment implies when omitted.

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 dense sentence with the return type front-loaded and the key constraint trailing. Nothing is wasted, though the trailing 'in the selected environment' is vague enough to be slightly hollow on its own.

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 a full output schema and 100% parameter coverage, the description only needs to frame the fetch-by-key contract, which it does. Minor gaps remain around how it differs from the other image-producing siblings, but nothing required for a correct call is missing.

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 detail, including the environment lookup path and the version-pinning rule. The description only echoes the 'exact stored page profile key' and 'selected environment' constraints, adding no syntax or format detail beyond the schema — baseline 3.

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 — return a captured viewport WebP — and scopes it to an exact stored page profile key from list_pages. That distinguishes it reasonably well from the many other image siblings (get_capture_image, get_click_image, get_page_evidence_image), though it never explicitly names which sibling covers those other image types.

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?

Points the agent at list_pages as the source of the profile key and mentions the environment selection, which implies the discovery-then-fetch workflow. It gives no explicit when-to-use versus the numerous other image tools, and no when-not-to-use or failure guidance.

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