Skip to main content
Glama
Sign In
chrome

chrome

by wellrccity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Screenshot

screenshot

Capture a browser viewport, full page, or specific element as a PNG or JPEG image the model can see. Add labeled element refs or a coordinate grid for precise visual analysis.

Instructions

Capture the viewport, the full page, or one element. Set annotate=true to draw element refs as labeled boxes and grid=true for a 100px coordinate grid. Returns an image the model can see.

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
refNoCapture a specific element by ref.
gridNoDraw a 100px coordinate grid.
tabIdNo
formatNopng
frameIdNo
qualityNo
timeoutNo
trustedNoForce CDP on/off for this capture.
annotateNoDraw boxes/labels for element refs.
fullPageNoCapture the entire scrollable page.
maxWidthNo
selectorNoCapture a specific element by CSS selector.
maxHeightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add one genuinely useful behavioral fact ('Returns an image the model can see'), but says nothing about permissions, the trusted/CDP toggle semantics, timeout behavior, or how quality/format affect the capture.

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?

Three tight sentences, no filler, with the capture scopes front-loaded and the flag behaviors following. Every sentence earns its place.

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?

With 13 parameters, no annotations, and no output schema, the description is only minimally sufficient. It usefully notes the image return value (which compensates for the missing output schema) but does not cover the majority of the parameters, leaving real gaps for a tool of this complexity.

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 coverage is only 46% and there are 13 parameters. The description adds meaning for grid, annotate, fullPage, and implicitly ref/selector, but leaves tabId, frameId, format, quality, timeout, trusted, maxWidth, and maxHeight undocumented in both schema and description.

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 a specific verb ('Capture') and resource ('viewport, full page, or one element'), and the three capture scopes are clearly itemized. It does not, however, distinguish itself from the sibling 'snapshot' tool, which an agent could reasonably confuse with a visual capture.

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?

The description explains what the annotate and grid flags do, which implies when to use them, but gives no guidance on when to choose screenshot over 'snapshot' or any other sibling. Usage is implied rather than stated, with no when-not conditions.

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