Extract visible text from web pages as plain text for AI agents. Target main content by default, or specify a CSS selector and character limit to control output.
Read the visible text of the page (main content by default) as plain text.
| Name | Required | Description | Default |
|---|---|---|---|
| maxChars | No | Default 8000. | |
| selector | No | CSS selector to read instead of the main content. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the return format (plain text) and the default scope (main content), which is useful, but says nothing about truncation via maxChars, permissions, or whether the read is purely side-effect-free.
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?
A single front-loaded sentence with the default scope in parentheses. No filler; every clause 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 read-only tool with no output schema or annotations, the description is adequate but thin. It does not explain that returned content is capped by maxChars (default 8000) or what the response structure looks like, leaving the agent to infer return behavior.
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?
Schema description coverage is 100%, so both parameters are already documented. The phrase 'main content by default' adds meaning to the selector parameter's default behavior, but maxChars and its truncation effect are not elaborated. Baseline 3 is appropriate.
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?
States a specific verb (read) and resource (visible text of the page), plus the default scope (main content) and output form (plain text). It is clear what the tool does, but it does not distinguish itself from overlapping siblings like snapshot or evaluate, which also surface page content.
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?
There is no explicit when-to-use, when-not, or alternative routing. An agent must infer that this is for extracting page text rather than choosing between read, snapshot, evaluate, or screenshot on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.