Mcp-DOM

Overview Schema Source Related Servers Discussions Admin

get_screenshots

Retrieve visual and screenshot checkpoints from a recording session to inspect UI states and diagnose layout changes or element disappearance.

Instructions

List visual checkpoints and screenshot checkpoints captured during the recording session.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "get_screenshots"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Session ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavior disclosure. It communicates that the tool is a read-only listing operation scoped to a recording session, but it does not describe the returned checkpoint structure, whether it returns metadata or image data, or behavior for empty or missing sessions. This is adequate but not richly transparent.

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?

One sentence with no filler. The key action and resource are front-loaded, and every word contributes to identifying what the tool does, making it appropriately concise for a simple listing operation.

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?

For a one-parameter list operation with no output schema or annotations, the description gives enough to select the tool: it names the resource and scope. However, it does not explain what distinguishes 'visual checkpoints' from 'screenshot checkpoints,' what fields are returned, or how results are ordered or served, leaving some ambiguity for the agent.

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?

The input schema already fully describes sessionId ('Session ID') with 100% coverage. The description adds only that the session is a 'recording session,' which is minor contextual value beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses the specific verb 'List' and names the resource ('visual checkpoints and screenshot checkpoints') with the scope 'captured during the recording session.' This clearly differentiates it from the capture_* sibling tools, which take live screenshots rather than listing recorded checkpoints.

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?

There is no explicit when-to-use guidance or mention of alternatives such as capture_page_screenshot or get_timeline. The phrase 'captured during the recording session' implies this is for already-recorded session data, but the description does not state when to prefer it over related tools or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.