Snap Screenshots

Take a screenshot

take_screenshot

Read-onlyIdempotent

Render a public web page in Chromium and return a screenshot. Use fullPage for the whole scrollable page; very tall pages come back as a link instead of an inline image, and a fullPage WebP capture of a page taller than 16383px is clipped to that height (reported as fullPageClip) — use jpeg or png for pages that tall.

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": {
      "url": "<url>"
    },
    "name": "take_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL to capture, e.g. 'https://example.com'.
`width`	No	Viewport width in CSS pixels. Values above the service maximum are clamped.
`format`	No	Image format. webp and jpeg are much smaller than png.	webp
`height`	No	Viewport height in CSS pixels. Values above the service maximum are clamped.
`locale`	No	BCP 47 locale, e.g. de-DE.
`fullPage`	No	Capture the full scrollable page.
`waitUntil`	No	Navigation event to wait for before capturing.	load
`timezoneId`	No	IANA time zone, e.g. Europe/Berlin.
`waitForSelector`	No	CSS selector that must appear before capturing.

Output Schema

Name	Required	Description	Default
`bytes`	Yes
`cache`	Yes
`width`	Yes
`height`	Yes
`inlined`	Yes
`imageUrl`	Yes
`contentType`	Yes
`fullPageClip`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 31, 2026

removedOutput schema / properties / height / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / height / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / width / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / width / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / height / description

Previous value: -"Viewport height in CSS pixels."New value: +"Viewport height in CSS pixels. Values above the service maximum are clamped."

changedInput schema / properties / height / maximum

Previous value: -1080New value: +9007199254740991

changedInput schema / properties / width / description

Previous value: -"Viewport width in CSS pixels."New value: +"Viewport width in CSS pixels. Values above the service maximum are clamped."

changedInput schema / properties / width / maximum

Previous value: -1920New value: +9007199254740991

addedOutput schema / properties / fullPageClip

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "captureHeightPx": {
+      "type": "number"
+    },
+    "pageHeightPx": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "captureHeightPx"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 5, 2026
- changedInput schema / properties / url / description
```
Previous value: -"Public http(s) URL to capture."New value: +"Public http(s) URL to capture, e.g. 'https://example.com'."
```
- addedInput schema / properties / url / format
```
Added value: +"uri"
```
- removedInput schema / properties / url / minLength
```
Removed value: -1
```
First observedSep 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses important edge behavior: very tall pages are returned as a link instead of inline, and fullPage WebP captures taller than 16383px are clipped with a fullPageClip report. This is exactly the kind of operational context an agent needs before calling the tool.

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?

The definition is two front-loaded sentences with no wasted text. Every clause contributes a useful constraint or edge case.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter screenshot tool with an output schema and read-only annotations, the description covers the key scope, format tradeoff, and tall-page return/clipping caveats. Nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all nine parameters and the baseline is 3. The description adds meaningful constraints for fullPage and format, including the tall-page clipping caveat, though it does not further explain the remaining parameters.

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 names a specific verb and resource: render a public web page in Chromium and return a screenshot. It is immediately clear what the tool does and is not confusable with the only sibling, get_quota.

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?

It gives explicit guidance for fullPage and for choosing jpeg/png over WebP when capturing very tall pages. It does not name when not to use the tool or an alternative, but no relevant alternative exists among the siblings.

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

All Snap Screenshots tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?