Skip to main content
Glama

extract_clean_text

Read-onlyIdempotent

Extract readable text or markdown from a page's main content and iframes, with a character cap to keep output compact for AI agents.

Instructions

Extract readable text or markdown from the main content and iframes, capped at maxChars.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNo
formatNotext
maxCharsNo
savePathNoFile under cwd or TURBO_BROWSER_SAVE_ROOT.
selectorNo
includeFramesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.1
    • changedInput schema / properties / savePath / description
      Previous value: -"Optional file path relative to cwd to save text output."New value: +"File under cwd or TURBO_BROWSER_SAVE_ROOT."
  2. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds scope detail (main content plus iframes) and the maxChars cap, but it never discloses that savePath causes a file write to disk, which is the one behavior not captured by the annotations.

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 front-loaded sentence with the core capability first and the cap constraint second, with no filler. It is efficient, though its brevity borders on under-specification given the six-parameter surface.

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?

For a six-parameter tool with no output schema and very low schema description coverage, one sentence is insufficient. An agent cannot learn from the description how selector narrows extraction, how includeFrames interacts with the stated iframe support, or that savePath writes results to disk.

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 description coverage is only 17% across six parameters, so the description must compensate but does not. It explains only maxChars (which is already a schema default) and format implicitly; tabId, selector, includeFrames, and savePath get no meaning from the description, leaving the file-path and frame-selection semantics entirely to bare schema types.

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 (extract) and resource (readable text or markdown from main content and iframes), so the agent knows exactly what the tool produces. It does not distinguish itself from potential siblings like capture_page or inspect_compact, so an agent cannot tell from the text alone which page-reading tool to prefer.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only implicit signal is 'main content and iframes', which hints at scope but leaves the agent to infer that this is the read-a-page-as-text tool versus the other page tools in the sibling list.

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