Skip to main content
Glama

Page snapshot

browser_snapshot
Destructive

Capture accessibility snapshot of the current page, this is better than screenshot. Takes the session_id from open_browser. 0.1¢ a step that runs.

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

Input Schema

NameRequiredDescriptionDefault
boxesNoInclude each element's bounding box as [box=x,y,width,height] in the snapshot. Coordinates are viewport-relative, in CSS pixels (Element.getBoundingClientRect)
depthNoLimit the depth of the snapshot tree
targetNoExact target element reference from the page snapshot, or a unique element selector
filenameNoSave snapshot to a file instead of returning it in the response. Relative file names are resolved against the workspace root.
session_idYesThe session id open_browser returned.

Output Schema

NameRequiredDescriptionDefault
urlNoThe address of the page after the step.
errorNoWhy the step failed, when it failed.
titleNoThe page title.
read_atNoWhen the page was read.
took_msNoHow long the step took.
price_usdNoWhat the step cost, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "The page after the step, and what the step cost.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the step failed, when it failed.",
      +      "type": "object"
      +    },
      +    "price_usd": {
      +      "description": "What the step cost, in dollars.",
      +      "type": "number"
      +    },
      +    "read_at": {
      +      "description": "When the page was read.",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "The page title.",
      +      "type": "string"
      +    },
      +    "took_ms": {
      +      "description": "How long the step took.",
      +      "type": "integer"
      +    },
      +    "url": {
      +      "description": "The address of the page after the step.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

The description adds genuinely useful context beyond the annotations: a per-step cost ('0.1¢ a step that runs') and the provenance of session_id. It does not address the tension with the supplied hints, which mark this capture operation as destructiveHint=true and non-idempotent, nor does it say whether the snapshot mutates page state or how large output is handled. The description does not explicitly assert read-only behavior, so this is an omission rather than a direct contradiction.

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?

Two short sentences, front-loaded with the action and the screenshot comparison. The trailing '0.1¢ a step that runs' is slightly awkward phrasing but carries real information, so little is wasted.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the annotations nominally cover the safety profile. Still, for a tool with five parameters and a destructive hint, the description says nothing about what the snapshot contains, how depth/target affect scope, or when to prefer a sibling like browser_find.

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%, so boxes, depth, target, filename, and session_id are already fully documented. The description only restates session_id provenance, which the schema itself already says ('The session id open_browser returned'), adding no new meaning. Baseline 3 applies.

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?

States a specific verb and resource ('Capture accessibility snapshot of the current page') and implicitly positions itself against browser_take_screenshot via 'this is better than screenshot'. It does not name the sibling explicitly, so an agent must infer the comparison, but the core action is unambiguous.

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?

'this is better than screenshot' gives a preference signal for one alternative, and 'Takes the session_id from open_browser' establishes the prerequisite. However, there is no guidance on when a snapshot is the wrong choice (e.g. versus browser_find, browser_read, or browser_evaluate) and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.