Skip to main content
Glama
chrome-fast
by ventos312

screenshot

Read-only

Capture the current page as a PNG or JPEG image, optionally the full scrollable page. Use it when visual layout matters, such as verifying rendering, spacing, or UI changes.

Instructions

Capture a screenshot of the current page as an image. Only use when visual layout matters; prefer get_page for most tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoImage format (default: png)
qualityNoJPEG quality 0-100 (default: 80); ignored for png
fullPageNoCapture the whole scrollable page instead of just the viewport (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the implicit cost/utility tradeoff by telling the agent this is only worthwhile when visual layout matters. It does not describe what the returned image payload looks like or any size/rate considerations, so it stops just short of full behavioral disclosure.

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?

Two sentences with zero filler: the action first, then the usage constraint and the alternative. Every clause carries decision-relevant information.

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 three-optional-parameter, no-output-schema tool, the description covers what is produced and when it is worth calling. It could note that the result is binary image content rather than page text, but the essentials for correct invocation are present.

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 format, quality, and fullPage are already fully documented with defaults and enum values. The description adds nothing about these options (e.g., when to prefer fullPage or jpeg quality), 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?

Names a specific verb and resource ('Capture a screenshot of the current page as an image') and scopes it to the current page, which distinguishes it from siblings like get_page or navigate. An agent can identify exactly what this produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the selection condition ('Only use when visual layout matters') and names the preferred alternative ('prefer get_page for most tasks'). This is the when-to-use plus alternative routing that most definitions omit.

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