Skip to main content
Glama

browser_snapshot

Read rendered page text, including off-screen content and shadow roots, plus viewport flags and scroll regions with target refs, positions, and directions. Refs expire on navigation.

Instructions

Read rendered document text (including off-screen content), viewport flags and scroll regions with target refs, positions and available directions. Includes open shadow roots. Refs expire on navigation.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
maxCharsNo
showScrollbarsNoOptional visual assistance: inject visible scrollbar styling. Ordinary snapshots do not change page styling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description does useful work by disclosing off-screen content inclusion, open shadow roots, and ref expiration on navigation. It still leaves important behavioral gaps: it does not explicitly state that the operation is read-only, does not describe response truncation or maxChars behavior, and only the schema mentions the showScrollbars styling side effect.

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?

The description is front-loaded with the main purpose and is free of filler, with each sentence contributing useful information. The first sentence is a dense noun list, but it remains purposeful and readable.

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?

For a tool with five parameters, no annotations, and no output schema, the description adequately characterizes the returned content and adds important lifecycle information about refs expiring. Parameter details are largely covered by the schema, though the description could do more to disclose truncation and mutation-safety behavior.

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 80%, so the schema already documents most parameters. The description does not add parameter-specific meaning beyond loosely referencing viewport flags and scroll regions; it does not explain tabId, browser, frameId, maxChars, or showScrollbars semantics beyond what the schema already provides.

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?

The description states a specific verb ('Read') and resource ('rendered document text') and adds concrete output details such as viewport flags, scroll regions, target refs, positions, directions, and open shadow roots. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like browser_accessibility or browser_screenshot.

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?

Usage is implied by 'Read rendered document text' and the note that refs expire on navigation gives a useful operational caveat. However, there is no explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions.

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