Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

take_snapshot

Captures a structured text snapshot of the page DOM, helping AI agents inspect and understand page content.

Instructions

Get a structured text snapshot of the page DOM (useful for AI understanding)

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only snapshot but does not explicitly state side effects, permissions, whether it uses the current tab by default, or what the snapshot includes.

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?

The description is a single front-loaded sentence with no unnecessary wording. The parenthetical adds a brief usage hint without bloating the definition.

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?

For a simple one-parameter read tool with no output schema, the description adequately states the return type. However, it omits when to use it versus similar sibling tools and does not clarify default tab 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 100%, and the single optional tabId parameter is documented in the schema. The description adds no additional meaning about tabId behavior, so the baseline of 3 is appropriate.

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 and resource: "Get a structured text snapshot of the page DOM." It is clear what the tool does, but it does not distinguish this from sibling tools such as get_page_content or get_accessibility_tree.

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?

The only usage hint is "useful for AI understanding," which does not explain when to choose this tool over alternatives. There is no guidance on exclusions, prerequisites, or sibling tools like get_page_content.

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