Skip to main content
Glama

Snapshot

browser_snapshot

Retrieve the current accessibility tree and element refs to address page elements correctly after each interaction.

Instructions

Return the current accessibility tree of the page with element refs. Elements are addressed by their ref in every other tool. Run this after every interaction.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the output is a state snapshot whose refs are the addressing substrate for all other tools, and that it goes stale after interactions — valuable behavioral context. It says nothing about output size, truncation on large pages, or whether the call is side-effect free, which matters for an unannotated 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?

Two short sentences, front-loaded with what is returned, then the addressing convention, then the invocation cadence. No filler or restatement of the title.

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?

No output schema exists, so the description must characterize the return value; "accessibility tree with element refs" does that at a workable level for a zero-parameter tool. The only real gap is output volume/shape detail (e.g., truncation or ref lifetime), which an agent would benefit from knowing before relying on refs across calls.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies no input is needed to produce the snapshot.

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 ("Return the current accessibility tree of the page") plus the key payload detail ("with element refs"). The clause "Elements are addressed by their ref in every other tool" separates it from siblings like browser_screenshot or browser_get_console_logs, which return different artifacts.

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?

Gives a clear, actionable trigger: "Run this after every interaction," which tells the agent when to call it in the interaction loop. It does not name a when-not condition or point to browser_screenshot for visual inspection, so it stops short of full alternative routing.

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