Skip to main content
Glama

page_text

Fetch the visible text from a specified browser tab or the last agent tab, using offset and maxChars to read long pages in manageable parts.

Instructions

Get the visible text of a page. Use offset to read long pages in parts.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.
offsetNoStart character. Default 0.
maxCharsNoDefault 20000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It indicates a read operation and the offset mechanism for pagination, but omits details like whether 'visible' excludes hidden elements, if it's read-only, or any side effects. Adequate but with clear gaps.

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 with zero waste. The core action is front-loaded, followed by a practical tip.

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 simple getter with no output schema and no annotations, the description covers the main purpose and a key pagination hint. It could be slightly more complete by clarifying the return format or visibility semantics, but it gives an agent enough to call it correctly.

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 100%, so the schema already documents all three parameters. The description adds a usage note for offset ('read long pages in parts'), which gives some meaning beyond the schema, but it doesn't mention tabId or maxChars. Baseline 3 is appropriate.

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?

The description states a specific verb ('Get') and resource ('visible text of a page'), making the core purpose clear. It doesn't explicitly differentiate from siblings like page_elements, but the resource is distinct enough.

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?

It offers a tip for reading long pages using offset, which is useful usage guidance. However, it doesn't say when to use this tool versus alternatives like page_elements or screenshot, nor does it state any exclusions.

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