Retrieve the visible text from the active browser page. Use this lighter alternative to aria snapshots for reading content or extracting page text, with optional character truncation.
Get the visible text (document.body.innerText) of the active page. Lighter than a full aria snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
| maxLength | No | Truncate to this many chars. Default 100000. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosure. It accurately identifies the data source (document.body.innerText) and performance character ('lighter'), but does not comment on side effects (expected none), return format, or edge cases like blank pages or wait behavior. The description is truthful but adds only modest behavioral context beyond the obvious read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no fluff. It front-loads the core purpose and immediately adds the differentiating performance note. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter with one well-documented optional parameter and no output schema, the description is sufficiently complete: it states what is returned (visible text), the source method, and a comparison to a related tool. It does not explain the return type (obviously a string) or truncation behavior, but the schema covers the truncation parameter, so the definition is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single parameter maxLength, including its default value. The tool description adds no parameter-specific meaning, but because the schema fully explains the parameter, the baseline of 3 applies without requiring compensation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get the visible text ... of the active page.' It also distinguishes itself from a heavier alternative by noting it is 'lighter than a full aria snapshot.' This makes the tool's purpose immediately clear and differentiable from browser_snapshot and similar siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool by framing it as a lighter alternative to a full aria snapshot, suggesting it is for cases where only visible text is needed. It does not explicitly name browser_snapshot or give a when-not-to-use condition, but the comparative hint provides clear context for selecting this over the heavier snapshot.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.