Skip to main content
Glama
Sign In

Shotlane

by dev.shotlane
OverviewDiscussionsAdmin

Screenshot a web page

screenshot
Read-only

Take a screenshot of a public web page and return it as an image you can look at. The user sees it in an inline viewer. Use it when the user asks for a screenshot or to see a page, including how it looks on a specific device such as an iPhone (set device), and for questions about how a page looks: layout or visual bugs, charts, images, or whether a deploy actually rendered. For page text, read_page returns Markdown. Uses 1 credit from the user's Shotlane account.

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL; https:// is assumed if omitted.
delayNoExtra wait after load in ms (0-10000).
widthNoViewport width in px (240-1920). Use 393 for a phone.
deviceNoShow the page as on this device (screen size and mobile mode). Overrides width and height.
heightNoViewport height in px (240-2160).
selectorNoOptional CSS selector to capture a single element.
dark_modeNo
full_pageNoCapture the whole scrollable page instead of just the viewport. Tall pages come back as several image slices so text stays readable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / device / enum
      Previous value: -[
-  "iphone",
-  "iphone_se",
-  "pixel",
-  "galaxy",
-  "ipad",
-  "laptop",
-  "desktop",
-  "desktop_hd"
-]New value: +[
+  "desktop",
+  "desktop_hd",
+  "laptop",
+  "ipad",
+  "iphone",
+  "iphone_se",
+  "pixel",
+  "galaxy",
+  "iphone_duo",
+  "iphone_duo_cover"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / device
      Added value: +{
+  "description": "Show the page as on this device (screen size and mobile mode). Overrides width and height.",
+  "enum": [
+    "iphone",
+    "iphone_se",
+    "pixel",
+    "galaxy",
+    "ipad",
+    "laptop",
+    "desktop",
+    "desktop_hd"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / width / description
      Previous value: -"Viewport width in px (240-1920). Use 390 for mobile."New value: +"Viewport width in px (240-1920). Use 393 for a phone."
  4. Changed1 schema field changed
    • changedInput schema / properties / full_page / description
      Previous value: -"Capture the whole scrollable page instead of just the viewport."New value: +"Capture the whole scrollable page instead of just the viewport. Tall pages come back as several image slices so text stays readable."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds meaningful context beyond them: the result is rendered in an inline viewer for the user, the page must be public, and the call costs 1 credit. It does not discuss failure modes (e.g. what happens on unreachable or auth-gated pages) or latency, so not a 5.

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?

Front-loaded with the core action and output, then routing guidance, then cost. Dense and mostly waste-free, though the device/visual-bug enumeration runs slightly long for what it delivers.

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?

With no output schema, the description does the needed work by explaining that an image is returned and shown in an inline viewer, and that full-page captures come back as several slices. What's missing is any note on errors or how long captures take, which matters for an open-world network tool.

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 88%, so most parameters are already documented. The description only adds marginal guidance by pointing at the `device` parameter for iPhone rendering, which the schema already explains in more detail. Baseline 3 is appropriate when the schema carries the weight.

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 ('Take a screenshot of a public web page') and the return type ('return it as an image you can look at'). Explicitly contrasts with read_page, so the agent can distinguish it from the closest sibling without opening either 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?

Gives concrete triggering conditions: user asks for a screenshot, wants to see a page, wants a specific device rendering, or asks about layout/visual bugs/charts/images/deploy rendering. Names the alternative ('For page text, read_page returns Markdown'), which is an explicit when-not-to-use rule.

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

All Shotlane toolsInspect
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