Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

snapshot

Retrieves the text content from a specified browser tab, enabling AI clients to inspect page content without parsing raw HTML.

Instructions

Get page text content

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": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden, yet it only implies read-only behavior through the verb "Get." It says nothing about whether the call waits for page load, whether hidden or off-screen text is included, whether output is truncated for large pages, or whether it requires the tab to be connected/attached.

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?

A single four-word sentence that is fully front-loaded with the resource and no filler. Its brevity is clean structurally, though it edges into under-specification rather than efficient density.

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

Completeness2/5

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

The tool is simple, but with no output schema and no annotations, the description is the only source of information about the returned payload — its format, scope, and size behavior — and it says nothing. An agent cannot predict what it will receive or how to decide between this and evaluate.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional tabId parameter, and the description does not compensate at all. It never explains what tabId identifies, nor what happens when it is omitted (presumably the active tab), which is the key ambiguity given the parameter is not required.

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 pairs a specific verb ("Get") with a specific resource ("page text content"), which usefully disambiguates the otherwise vague name "snapshot" — an agent can tell this returns text, not an image or a state dump. It does not differentiate itself from siblings that could also surface page text (e.g. evaluate), and leaves the scope (whole document vs visible viewport vs selected element) unspecified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of any alternative sibling such as screenshot or evaluate. The agent is left to infer that this is the text-reading counterpart to those tools from the name alone.

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