Skip to main content
Glama

Snapshot the current page

browser_snapshot

Re-distills the current page into fresh Semantic Markdown with updated [eN] references and optionally captures a PNG screenshot for canvas or vision workflows.

Instructions

Re-distil the current page and return a fresh Semantic Markdown snapshot with updated [eN] references. Also able to capture a PNG screenshot (useful for applications or vision workflows).

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
scopeNoOnly include content matching these terms.
fullPageNoCapture the full scrollable page instead of the viewport.
screenshotNoAlso return a PNG screenshot of the viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 does disclose the useful behavioral fact that references are regenerated ('fresh ... with updated [eN] references'), which tells the agent old refs may be stale. It says nothing about side effects, cost/latency, or whether the snapshot reflects the live DOM, which matters for a no-annotation tool.

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 sentences, front-loaded with the primary return value, then the optional capability. Minimal waste; only the slightly loose phrasing 'Also able to capture' could be tightened.

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 simple tool with zero required parameters, full schema coverage, and no output schema, the description covers what comes back and the optional screenshot mode. Remaining gaps—whether the page must already be navigated and any cost of re-distilling—are minor but non-trivial given the absence of annotations.

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 coverage is 100%, so the schema already documents scope, fullPage, and screenshot. The description only adds rationale for the screenshot flag ('useful for <canvas> applications or vision workflows'); scope's term-matching behavior and fullPage's interaction with the viewport note are left entirely to the schema.

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 gives a specific verb and result: 'Re-distil the current page and return a fresh Semantic Markdown snapshot with updated [eN] references', and adds the optional PNG capture. The intent to refresh an already-loaded page (rather than navigate) is clear without opening the schema, though no sibling is named for contrast.

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 context is implied by 'Re-distil the current page' and the parenthetical that screenshots are 'useful for <canvas> applications or vision workflows'. There is no explicit statement of when to call this versus browser_navigate or browser_batch, and no exclusions or prerequisites (e.g., a page must already be loaded).

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