Skip to main content
Glama

browser_get_page

browser_get_page
Read-onlyIdempotent

Read page metadata and viewport state for a Chrome tab or frame, so agents can check the current document context before acting.

Instructions

Read page metadata and viewport state.

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_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idNoChrome tab ID. Defaults to the active tab when omitted.
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say which metadata fields are returned, what "viewport state" includes, or that frame_id scopes the read to a single frame. For a read tool with no output schema, the behavioral surface is under-described.

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 front-loaded sentence with zero filler. It is efficient, though its brevity borders on under-specification rather than true economy.

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?

There is no output schema, so the description is the only source for what this tool returns, yet it says only "page metadata and viewport state" without enumerating fields. For a four-parameter tool whose entire value is its return payload, this leaves the agent guessing about what it will actually get back.

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%, so tab_id, frame_id, session_id, and session_name are all documented in the schema itself, including defaults and stickiness. The description contributes no additional parameter meaning, which is the baseline 3 when the schema does the work.

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?

"Read page metadata and viewport state" names a specific verb (read) and resource (page metadata/viewport), and the use of "metadata" implicitly distinguishes it from browser_get_page_content and browser_get_frames. It never names a sibling explicitly, so an agent must infer the boundary from the noun choice alone.

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 exclusion, and no mention of when to prefer browser_get_page_content, browser_get_frames, or browser_observe instead. The agent is left to infer selection purely from tool names.

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