Skip to main content
Glama

Get replay step image

get_replay_step_image
Read-onlyIdempotent

Return the after.webp captured for one replay step, when present.

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>",
      "replay": "<replay>",
      "step": "<step>"
    },
    "name": "get_replay_step_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYesOne-based scenario or replay step index from its manifest steps[].index. Must be at least 1 and identify a recorded step.
replayYesStored replay key returned by list_replays for the selected product version.
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. Changed5 schema fields changed
    • addedInput schema / properties / product / description
      Added value: +"Product key, for example finance-ozon-ru"
    • addedInput schema / properties / replay / description
      Added value: +"Stored replay key returned by list_replays for the selected product version."
    • addedInput schema / properties / step / description
      Added value: +"One-based scenario or replay step index from its manifest steps[].index. Must be at least 1 and identify a recorded step."
    • 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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile needs no restating. The description adds one useful behavioral fact beyond them -- that the image is only available 'when present', i.e. some steps have no capture -- but says nothing about what happens when absent (error vs empty result) or about the webp format's resolution/size.

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?

A single front-loaded sentence of roughly a dozen words, with the artifact name and the availability caveat in the right order and no redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the four required parameters are documented in the schema. However, for a tool whose defining edge case is a missing capture, the description never states the failure behavior, and it gives no hint that before/after variants may exist, leaving the agent to guess among near-identical 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 the optional environment and the one-based step index) are already fully documented in the schema. The description adds no syntax, format, or defaulting guidance beyond it, which is acceptable but earns only the baseline.

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 the after.webp captured for one replay step') and names the concrete artifact returned, which distinguishes it from generic asset getters. It does not explicitly contrast with the very similar sibling get_scenario_step_image or with get_replay_step (which returns step metadata), so the differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage hint is the qualifier 'when present', which warns that the image may not exist but gives no when-to-use, prerequisites, or alternative routing. An agent must infer from siblings that get_replay_step returns step data while this returns its screenshot.

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