Skip to main content
Glama
Sign In
zen-browser

zen-browser

by grapedjuice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_page_text

Extract readable text from a browser page instead of raw HTML, prioritizing main or article content for summarization or analysis.

Instructions

Extract the readable text of the page (main/article content first).

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": "get_page_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab to act on. Defaults to the active tab of the focused Zen window.
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Extract' implies a read-only operation, but the description never confirms it, never explains what happens with hidden or lazy-loaded content, and never mentions that max_chars can truncate output. For a scraping tool with zero annotation coverage this is a meaningful gap.

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 tight sentence with the core action and its priority rule front-loaded, and no wasted words. It is arguably too terse rather than bloated, but structurally it is clean.

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?

With no annotations and no output schema, the description must explain both behavior and return shape, and it does neither. An agent cannot tell whether the result is plain text, whether it is truncated by max_chars, or what happens on pages with no article content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: tabId is documented in the schema, but max_chars has no description anywhere. The tool description mentions no parameters at all, so it does not compensate for the undocumented max_chars parameter or explain its truncation semantics.

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?

Names a specific verb and resource: 'Extract the readable text of the page', with a scoping clause '(main/article content first)' that signals the extraction strategy. An agent can distinguish it from screenshot or javascript siblings, though it is not explicitly contrasted with read_page or find, which are the closest neighbors.

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 guidance on when to choose this over read_page, find, screenshot, or javascript. The parenthetical hints at content prioritization but says nothing about whether this is the right tool for full-page dumps versus targeted element lookup, and no prerequisites or exclusions are stated.

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

Deploy Server

Other Tools