Skip to main content
Glama
Sign In
agent-browser

agent-browser

by EgiStr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

page_snapshot

Captures visible text and numbered interactive elements from the agent tab, returning click/type references for reliable browser actions.

Instructions

Visible text plus numbered interactive elements of the agent tab, for click/type_text refs.

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

Input Schema

NameRequiredDescriptionDefault
max_elementsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/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 discloses the returned content (visible text plus numbered elements), which is useful, but says nothing about whether it is read-only, how stale the snapshot can be, or what happens when the element list is truncated by the limit.

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?

One compact sentence with the content description front-loaded and no filler. Nothing 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-value detail is rightly omitted, but for a tool with an undocumented limit parameter and no annotations, the description should explain truncation or ordering of refs. It is adequate but leaves a real gap.

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 max_elements parameter, and the description never mentions it. The 150 default and what happens when the limit is hit are documented nowhere, so the description fails to compensate for the schema gap.

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 resource and output shape: visible text plus numbered interactive elements of the agent tab. The phrase 'for click/type_text refs' clarifies the downstream use, which distinguishes it from screenshot or evaluate without naming them explicitly.

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?

The 'for click/type_text refs' clause implies the agent should call this before click or type_text, but it never states when not to use it or how it compares to screenshot or evaluate. Usage is implied rather than explicit.

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

Deploy Server

Other Tools