Skip to main content
Glama
Silbercue

Public Browser

by Silbercue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

view_page

Inspect page content and retrieve stable element references for click, type, and fill_form actions. Filter by interactive, all, landmark, or visual views, and expand collapsed containers for deeper access.

Instructions

See what is on the page: text plus stable element refs for click/type/fill_form. Default filter 'interactive' lists actionable elements; for paragraphs or table cells call view_page(ref, filter: 'all'). Collapsed containers show as [eXX role, N items] — expand with view_page(ref: 'eXX', filter: 'all').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoElement ref for a subtree
depthNoTree levels shown; indentation only, hidden sections need a click
filterNointeractive | all | landmark | visual (bounds, click point, visibility)interactive
max_tokensNoToken budget; content downsampled. Omit for full output

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.10.5
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / depth / description
      Previous value: -"Nesting depth — how many tree levels to display (default: 3). Controls indentation, not visibility. Hidden sections (display: none) require clicking tabs/buttons to reveal."New value: +"Tree levels shown; indentation only, hidden sections need a click"
    • changedInput schema / properties / filter / description
      Previous value: -"Filter mode: interactive (default), all, landmark, or visual (adds bounds/click/visibility)"New value: +"interactive | all | landmark | visual (bounds, click point, visibility)"
    • changedInput schema / properties / max_tokens / description
      Previous value: -"Token budget — page content is automatically downsampled to fit. Omit for full output."New value: +"Token budget; content downsampled. Omit for full output"
    • changedInput schema / properties / ref / description
      Previous value: -"Element ref (e.g. 'e5') to get subtree for"New value: +"Element ref for a subtree"
  2. First observedv2.7.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses that the output includes stable refs, that collapsed containers show summaries like '[eXX role, N items]', and that follow-up expansion calls are possible. This is meaningful behavior beyond the schema and helps the agent anticipate output shape.

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?

Three sentences, each earning its place: the core purpose comes first, then filter usage, then expansion behavior. There is no filler or redundant restatement of the schema.

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 an inspection tool with four optional parameters and no output schema, the description is largely sufficient: it specifies the return content, default behavior, and how to get broader or expanded views. The main gap is the absence of explicit differentiation from sibling inspection tools, but the core calling pattern is fully covered.

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?

Schema description coverage is 100%, so a baseline of 3 applies. The description adds practical meaning by mapping the 'filter' parameter to specific scenarios and explaining how 'ref' is used to expand collapsed subtrees, going beyond the schema's enum descriptions.

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?

The description states a specific action and resource: 'See what is on the page: text plus stable element refs for click/type/fill_form.' It clearly communicates what the tool returns and why it is useful, distinguishing its role from generic page-capture tools even without naming a sibling.

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?

The description gives explicit guidance for variant usage: default filter 'interactive' lists actionable elements, filter 'all' is for paragraphs/table cells, and collapsed containers are expanded via view_page(ref, filter: 'all'). It does not compare against sibling inspection tools like dom_snapshot or observe, but it clearly tells the agent when to adjust the call.

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