Skip to main content
Glama

Page Screenshot

page_screenshot
Read-only

Capture a page’s full canvas as viewers see it after data loads, so you can verify layout and visual design after edits.

Instructions

Image of a page's whole canvas as viewers will see it (draft content, after data loads). Use it to check layout and visual design after edits. Read-only.

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": {
      "page_id": "<page_id>"
    },
    "name": "page_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
qualityNo
report_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description's 'Read-only' merely repeats that. What it adds beyond the annotations is genuinely useful state information: the capture reflects draft content rendered after data loads, and covers the whole canvas rather than the visible viewport. It says nothing about latency, size limits, or what happens if data fails to load, but the rendering-state caveat is the key behavioral fact.

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?

Two short sentences, front-loaded with the resource and output, then the usage cue. The trailing 'Read-only.' is redundant with the annotation and slightly wastes a slot, but overall there is no padding.

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?

There is no output schema, and the description does at least characterize the return value as a full-canvas image of the draft state. However, for a 3-parameter tool with zero schema documentation, it leaves quality/report_id behavior and the image format/size entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters, so the description carries the full burden and does not meet it. It never explains 'quality' (presumably image compression) or 'report_id', leaving the agent to guess at their effect. Only 'page_id' is inferable from context.

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 the specific resource (a page's whole canvas) and the exact return type (an image as viewers will see it), which separates it from data-returning siblings like page_get. The verb is implicit ('Image of...') rather than an explicit 'capture', but the resource and output are unambiguous.

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 a clear usage context: 'Use it to check layout and visual design after edits.' That tells the agent when this tool is the right choice. It stops short of naming an alternative or a when-not condition, so it falls 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.

Deploy Server

Other Tools