Skip to main content
Glama

Get page evidence data

get_page_evidence_data
Read-onlyIdempotent

Return one evidence JSON file for a page view: nodes revealed by hover or click (reveal-.json, same node shape as elements with anchorPath to the captured parent), the inspected document of an embedded frame (frame-.json) or the layout at an extra viewport width (viewport-*.json rows keyed by element path).

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

Input Schema

NameRequiredDescriptionDefault
fileYesFile name from get_page_summary.evidence or element fields (stateCatalog.screenshots, states[].screenshot, reveals[].file/screenshot, frame.file/screenshot, themeScreenshots, viewportVariants), for example state-12-hover.webp or reveal-12-click.json.
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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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: +"Evidence JSON: revealed nodes, an embedded frame inspection or a viewport-width layout"
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Evidence JSON: revealed nodes, an embedded frame inspection or a viewport-width layout",
      -  "properties": {},
      -  "type": "object"
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine domain context about the shape of returned data (nodes carry anchorPath to the captured parent; viewport rows are keyed by element path), but says nothing about behavior when a file is absent or mismatched with the version. With an output schema present, return-value detail is partly redundant.

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 sentence, front-loaded with the core action, with the three file variants delivered as tight parentheticals. There is no filler, hedging, or repetition, and every clause adds a distinct file type.

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 single-file fetch with a full output schema, 100% parameter coverage and existing annotations, the description supplies enough to call it correctly; only the version/environment pinning nuance lives solely in the schema. It stops short of connecting the tool to its sibling image/asset fetchers, which a complex 6-parameter ecosystem arguably warrants.

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 six parameters (including the optional environment) are already documented in the schema, making 3 the baseline. The description's only added semantic value is correlating the file families to allowed filename patterns, which the schema's file description already does with more examples.

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?

The description states a specific verb and resource ('Return one evidence JSON file for a page view') and enumerates the three file families it covers (reveal-*.json, frame-*.json, viewport-*.json), so an agent knows exactly what artifact comes back. It does not name the closest sibling (get_page_evidence_image) to draw the JSON-vs-image boundary explicitly, which keeps it from a 5.

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?

Usage is only implied: the file families suggest this is the companion fetch to get_page_summary.evidence, but the description never says when to choose this over get_page_evidence_image, get_capture_asset, or get_page_artifacts. No prerequisites or exclusions are stated in the description itself.

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