Skip to main content
Glama

browser_get_page_content

browser_get_page_content
Read-onlyIdempotent

Extract readable text from a browser tab, plus optional HTML, image, and iframe metadata. Target a specific frame when app shells hide real content inside an iframe.

Instructions

Extract readable page text, and optionally HTML, image, and iframe metadata. Covers the top document unless frame_id targets a frame; app shells keep their real content inside an iframe, so check browser_get_frames when the text looks like navigation only.

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": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_get_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
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.
include_htmlNo
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.
include_framesNo
include_imagesNo
max_text_lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuine behavioral insight beyond that: extraction is scoped to the top document by default and single-page-app content may sit in an iframe, which explains empty/navigation-only results. It still says nothing about truncation behavior or result size despite max_text_length existing.

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?

Two sentences, zero filler, with the primary capability and its default scope front-loaded before the sibling redirect. Every clause carries actionable information.

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?

With 8 parameters, no output schema, and only 50% schema description coverage, the description covers the important conceptual pieces: what is extracted, what the optional flags add, and the iframe pitfall. The main residual gap is the absence of any note on truncation or how max_text_length affects results.

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 coverage is 50%, and the description maps the optional include_html / include_images / include_frames flags to the metadata they return, plus explains frame_id targeting. tab_id, session_id, session_name, and max_text_length get no mention in the description, though the schema documents most of them. This compensates partially but not fully for the coverage 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 verb and resource: extract readable page text plus optional HTML, image, and iframe metadata. It also scopes the operation (top document by default, a specific frame when frame_id is set), which separates it from browser_get_frames. It does not distinguish itself from the sibling browser_get_page, leaving a small ambiguity about which of the two to pick for a plain read.

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?

Gives a concrete redirect rule: check browser_get_frames when the extracted text looks like navigation only, because app shells keep content in an iframe. The default-target rule (top document unless frame_id) also tells the agent when the default is sufficient. It lacks an explicit statement of when not to use this tool at all (e.g. versus browser_get_interactives or browser_get_page).

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