Skip to main content
Glama
LvcidPsyche

Auto-Browser

by LvcidPsyche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

browser.screenshot

Read-only

Capture the current browser viewport as an image and get its artifact URL, skipping the full observe payload. Ideal for quick visual checks or sharing snapshots.

Instructions

Capture the current viewport and return it as an image (plus its artifact URL), without the full observe payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoWord added to the screenshot's file name.manual
session_idNoTarget session id, from browser.create_session or browser.list_sessions. Optional when exactly one session is live; observe and act tools create one when none is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1
  2. Removedv1.4.2
  3. Changed3 schema fields changedv1.0.3
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / session_id / maxLength
      Added value: +120
    • addedInput schema / properties / session_id / minLength
      Added value: +1
  4. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it captures only the current viewport and returns an image plus artifact URL rather than the full observe payload. It does not discuss auth or rate limits, but that is acceptable for a simple read-only capture 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 description is a single sentence with no filler. It front-loads the action and return value, then adds the key differentiator from observe. Every part earns its place.

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 simple read-only tool with two optional parameters fully documented in the schema, the description is complete. It states what is captured, what is returned, and how it differs from the main sibling. The absence of an output schema is mitigated by explicitly naming the return type.

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%, with both label and session_id already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Capture') and resource ('the current viewport'), and states the return value ('an image plus its artifact URL'). It also distinguishes itself from browser.observe by noting it lacks the full observe payload, so an agent can tell it apart from siblings 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 Guidelines4/5

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

The phrase 'without the full observe payload' clearly positions this as the lightweight image-only alternative to browser.observe. It does not explicitly say 'use this when you only need a screenshot' or list exclusions, but the contrast with observe gives sufficient contextual guidance for selection.

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