Skip to main content
Glama

Get recorded scenario scene

get_scenario_scene
Read-onlyIdempotent

Export a manually recorded scenario as canonical Scene with all referenced screen frames and observed transitions. Available only for a published version after human Admin review/redaction. Read list_scenarios and get_scenario_manifest to select an existing manual scenario. Frames are read from current page artifacts so manual blur cannot leave an old text copy in a flow export. Missing animation or intermediate interaction evidence remains unknown.

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

Input Schema

NameRequiredDescriptionDefault
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.
scenarioYesExact manual scenario ID from list_scenarios or its saved manifest.
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
uriYesuri
pageYespage
pathYespath
viewYesview
bytesYesbytes
issuesYes
schemaYesschema
sha256Yessha256
productYesproduct
versionYesversion
downloadNo
schemaUriYes
truncatedYesAt least one scene frame was truncated
assetCountYesassetCount
frameCountYes
issueCountYes
schemaPathYes
environmentYesenvironment
instructionYesinstruction
profileCountYes
schemaSha256Yes
artifactSchemaYes
issuesTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
      +  "download": {
      +    "additionalProperties": true,
      +    "description": "Signed links for clients without the bearer token. Present on authenticated HTTP calls when signed downloads are enabled.",
      +    "properties": {
      +      "baseUrl": {
      +        "description": "Append any relative /mcp-transfers/ or /mcp-assets/ URI to this base",
      +        "type": "string"
      +      },
      +      "expiresAt": {
      +        "description": "ISO 8601 expiry of every link in this object",
      +        "type": "string"
      +      },
      +      "instruction": {
      +        "description": "How to use the links",
      +        "type": "string"
      +      },
      +      "schemaUrl": {
      +        "description": "Signed absolute URL of schemaUri",
      +        "type": "string"
      +      },
      +      "starterUrl": {
      +        "description": "Signed absolute URL of starterUri",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Signed absolute URL of uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "baseUrl",
      +      "expiresAt",
      +      "instruction"
      +    ],
      +    "type": "object"
      +  }
      +}
    • removedOutput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Artifact manifest for the canonical Scene of a published manual scenario; page identifies the scenario and view is scenario."
    • addedOutput schema / properties / artifactSchema
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / assetCount
      Added value: +{
      +  "description": "assetCount",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / bytes
      Added value: +{
      +  "description": "bytes",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / download
      Added value: +{
      +  "$ref": "#/$defs/download"
      +}
    • addedOutput schema / properties / environment
      Added value: +{
      +  "description": "environment",
      +  "type": "string"
      +}
    • addedOutput schema / properties / frameCount
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / instruction
      Added value: +{
      +  "description": "instruction",
      +  "type": "string"
      +}
    • addedOutput schema / properties / issueCount
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / issues
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "frameId": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "nodeId": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "message"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / issuesTruncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "description": "page",
      +  "type": "string"
      +}
    • addedOutput schema / properties / path
      Added value: +{
      +  "description": "path",
      +  "type": "string"
      +}
    • addedOutput schema / properties / product
      Added value: +{
      +  "description": "product",
      +  "type": "string"
      +}
    • addedOutput schema / properties / profileCount
      Added value: +{
      +  "type": "integer"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "description": "Artifact manifest for the canonical Scene of a published manual scenario; page identifies the scenario and view is scenario.",
      -  "properties": {
      -    "artifactSchema": {
      -      "type": "string"
      -    },
      -    "assetCount": {
      -      "description": "assetCount",
      -      "type": "integer"
      -    },
      -    "bytes": {
      -      "description": "bytes",
      -      "type": "integer"
      -    },
      -    "environment": {
      -      "description": "environment",
      -      "type": "string"
      -    },
      -    "frameCount": {
      -      "type": "integer"
      -    },
      -    "instruction": {
      -      "description": "instruction",
      -      "type": "string"
      -    },
      -    "issueCount": {
      -      "type": "integer"
      -    },
      -    "issues": {
      -      "items": {
      -        "properties": {
      -          "code": {
      -            "type": "string"
      -          },
      -          "frameId": {
      -            "type": "string"
      -          },
      -          "message": {
      -            "type": "string"
      -          },
      -          "nodeId": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "code",
      -          "message"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "issuesTruncated": {
      -      "type": "boolean"
      -    },
      -    "page": {
      -      "description": "page",
      -      "type": "string"
      -    },
      -    "path": {
      -      "description": "path",
      -      "type": "string"
      -    },
      -    "product": {
      -      "description": "product",
      -      "type": "string"
      -    },
      -    "profileCount": {
      -      "type": "integer"
      -    },
      -    "schema": {
      -      "description": "schema",
      -      "type": "string"
      -    },
      -    "schemaPath": {
      -      "type": "string"
      -    },
      -    "schemaSha256": {
      -      "type": "string"
      -    },
      -    "schemaUri": {
      -      "type": "string"
      -    },
      -    "sha256": {
      -      "description": "sha256",
      -      "type": "string"
      -    },
      -    "truncated": {
      -      "description": "At least one scene frame was truncated",
      -      "type": "boolean"
      -    },
      -    "uri": {
      -      "description": "uri",
      -      "type": "string"
      -    },
      -    "version": {
      -      "description": "version",
      -      "type": "string"
      -    },
      -    "view": {
      -      "description": "view",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "schema",
      -    "product",
      -    "version",
      -    "page",
      -    "view",
      -    "environment",
      -    "path",
      -    "uri",
      -    "sha256",
      -    "instruction",
      -    "bytes",
      -    "assetCount",
      -    "truncated",
      -    "issues",
      -    "frameCount",
      -    "profileCount",
      -    "artifactSchema",
      -    "schemaPath",
      -    "schemaUri",
      -    "schemaSha256",
      -    "issueCount",
      -    "issuesTruncated"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / schema
      Added value: +{
      +  "description": "schema",
      +  "type": "string"
      +}
    • addedOutput schema / properties / schemaPath
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / schemaSha256
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / schemaUri
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / sha256
      Added value: +{
      +  "description": "sha256",
      +  "type": "string"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "description": "At least one scene frame was truncated",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / uri
      Added value: +{
      +  "description": "uri",
      +  "type": "string"
      +}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "version",
      +  "type": "string"
      +}
    • addedOutput schema / properties / view
      Added value: +{
      +  "description": "view",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "schema",
      +  "product",
      +  "version",
      +  "page",
      +  "view",
      +  "environment",
      +  "path",
      +  "uri",
      +  "sha256",
      +  "instruction",
      +  "bytes",
      +  "assetCount",
      +  "truncated",
      +  "issues",
      +  "frameCount",
      +  "profileCount",
      +  "artifactSchema",
      +  "schemaPath",
      +  "schemaUri",
      +  "schemaSha256",
      +  "issueCount",
      +  "issuesTruncated"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds real behavioral context beyond the read-only/idempotent annotations: the tool only works on published, admin-reviewed versions, frames are re-read from current page artifacts so redaction is applied at export time, and missing animation or intermediate interaction evidence remains unknown. Those are material caveats about availability and output fidelity that annotations cannot convey.

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?

Front-loads the core action in the first sentence, then layers availability, selection routing, and caveats in an efficient order. The final sentence about missing animation evidence is terse to the point of being slightly opaque, but nothing is 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 values, and it covers the prerequisites an agent must check before calling. It leaves the relationship to the sibling scene/interface tools implicit, which is the main remaining gap for a tool in such a crowded family.

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 product, version, scenario, and environment are already documented, including the 'do not use latest as an alias' and environment-selection rules. The description only points at which tools supply the scenario ID, which the schema already states. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource — export a manually recorded scenario as a canonical Scene with all referenced screen frames and observed transitions. Distinguishes itself from get_scenario_manifest/get_scenario_step by being the full scene export, and the 'manual scenario' qualifier separates it from interface-scene export.

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?

Gives concrete routing: read list_scenarios and get_scenario_manifest to pick an existing manual scenario, and states the availability precondition (published version after Admin review/redaction). It does not explicitly say when to prefer this over get_interface_scene or the per-step scenario tools, which keeps it short of a 5.

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