Skip to main content
Glama

browser_get

Read-onlyIdempotent

Read one element without writing JS. what: 'text' (innerText), 'html' (outerHTML), 'value' (input value), 'attribute' (needs name), 'box' (x, y, width, height in the viewport), 'state' (visible, enabled, editable, checked). ref is an aria-ref or CSS selector; frame = CSS selector of the it is in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>",
      "ref": "<ref>"
    },
    "name": "browser_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
nameNo
whatNotext
frameNo
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent operation. The description adds useful behavioral detail by explaining what each read mode returns, such as innerText for `text`, outerHTML for `html`, and viewport dimensions for `box`, though it does not describe error behavior when a ref or frame is missing.

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 dense and front-loaded, starting with the core action and then mapping each relevant parameter to its meaning. The backticked values make the mode list easy to scan without unnecessary prose.

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 a browser-reading tool with no output schema, the description explains the important return semantics of each `what` mode and the selector/frame formats. It is nearly complete, but the required `page_id` parameter and failure behavior are not addressed.

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 low, and the description compensates well for most core parameters by defining `what` values, `ref` formats, `frame` semantics, and the need for `name` with `attribute`. It still leaves `page_id` unexplained, though `in_workspace` is covered by the schema.

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 verb and resource: 'Read one element'. It also distinguishes the operation from JavaScript execution with 'without writing JS' and enumerates the readable aspects, so an agent can identify the tool's role without opening the schema.

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 first sentence establishes a clear context for use: reading a single element without writing JavaScript. The `what` options further imply the situations this tool covers, but the description does not explicitly say when to choose a sibling tool or when not to use this one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.