Skip to main content
Glama

session_screenshot

Captures the current page of an open browser session and returns it inline as an image, so you can visually inspect layout, images, captcha, or rendering.

Instructions

Take a screenshot of the session's current page and return it as an image.

Use it when you need to SEE the page (layout, images, a captcha, whether something rendered); session_snapshot is cheaper for reading text and finding selectors. Requires a session opened with profile_start first. The image comes back inline — nothing is written to disk.

Size is capped so it does not flood your context: at most 2000 px on the longest side, in CSS pixels. A full page bigger than that falls back to the visible viewport (scroll with session_eval, e.g. "window.scrollBy(0, innerHeight)", and take another); a PNG over 1 MB is re-taken as JPEG. What happened is said in the returned info.

Args: name: identity name, exactly as profiles_list reports it. full_page: true for the whole scrollable page, false (default) for what is visible in the window.

Returns the image, then {format, width, height, full_page, bytes, note?}. Fails with a readable message if the session is not open (409 — call profile_start first), the identity does not exist (404), or the visible window itself is over 2000 px (needs Nullprint 0.2.31+ on high-DPI displays; otherwise make the window smaller).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
full_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: inline image with nothing written to disk, a 2000 CSS-px cap on the longest side, viewport fallback for oversized pages, PNG-over-1MB re-encoded as JPEG, and a returned info field reporting what happened. It further documents failure modes (409 not-open, 404 missing identity) and a high-DPI limitation requiring a newer server version.

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?

Content is front-loaded with the action, then the when-to-use decision, then behavioral limits, with Args and Returns broken out into scannable blocks. Every sentence carries actionable detail — caps, fallbacks, error codes — and none is filler.

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?

There is no output schema, but the description documents the return shape itself (image plus {format, width, height, full_page, bytes, note?}). For a two-parameter tool with no annotations, this covers prerequisites, limits, fallbacks, and error behavior — an agent needs nothing else to call it correctly.

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

Parameters5/5

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

Schema coverage is 0% — the schema only carries bare titles — so the description must compensate, and it does. 'name' is defined as the identity name exactly as profiles_list reports it, and 'full_page' as true for the whole scrollable page versus the default visible window, which is precisely the ambiguity the bare boolean leaves open.

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 opening sentence states a specific verb+resource ('Take a screenshot of the session's current page') plus the return medium ('as an image'). It also explicitly distinguishes itself from session_snapshot, so an agent can route between the two 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?

It gives the positive trigger ('when you need to SEE the page — layout, images, a captcha, whether something rendered') and the cheaper alternative for text/selector work (session_snapshot). It also states the prerequisite (session opened with profile_start) and how to handle a full page that exceeds the cap (scroll with session_eval and re-take).

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