Skip to main content
Glama

View a check screenshot

view_check_screenshot

View the actual screenshot from a monitor check (current, previous, or diff) to see what a page looks like now and judge whether a change matters.

Instructions

Returns the actual screenshot image from a check, so you can SEE the monitored page rather than infer it from a diff percentage. view: 'current' (the page as of this check), 'previous' (the page before it), or 'diff' (the two composited with changes highlighted). Pass checkId 'latest' to see the current state of a monitor without looking up a check id first. Use this to answer 'what does the page look like now?', to judge whether a reported change actually matters, and to work out the right CSS selector for an action or extractor by looking at the layout.

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": {
      "uuid": "<uuid>"
    },
    "name": "view_check_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)
viewNoWhich image: 'current' (default), 'previous', or 'diff' with changes highlighted
checkIdNoCheck id (from get_check_history), or 'latest' for the most recent completed check. Defaults to 'latest'.
maxWidthNoLongest width to scale to, default 1200, max 4000
maxHeightNoHeight bound, default 3000, max 4000. Full-page captures are very tall, so this is what usually decides the scale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the return value is an actual image rather than a metric, the three view modes composite changes differently, and maxHeight usually drives scale for tall full-page captures. It omits image format/size limits beyond the schema and error behavior when no check exists.

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?

Purpose is front-loaded in the first clause and the sentences are dense with useful content. The middle sentence re-enumerating view modes largely duplicates the schema enum, which is the main redundancy.

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 five-parameter read tool with no output schema, the description establishes what is returned (an image), how to get the latest without an id lookup, and how scaling behaves. Minor gaps around returned image encoding and failure cases keep it from a 5.

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, including the 'latest' default and scaling bounds. The description restates the view modes and 'latest' shortcut with only marginal added meaning, so 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?

States a specific verb and resource ('Returns the actual screenshot image from a check') and contrasts it with inference from a diff percentage, which cleanly separates it from diff/metadata siblings like get_check or get_check_history.

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 when-to-use scenarios: answering 'what does the page look like now?', judging whether a reported change matters, and picking CSS selectors by inspecting layout. It lacks explicit when-not guidance or a named alternative for metadata-only questions, so it stops 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.