Skip to main content
Glama

kloakt_extract

Extract clean markdown content from web pages using a headless browser with full JavaScript rendering. Automatically strips navigation, headers, and footers for focused reading.

Instructions

Extract clean markdown content from a web page using a headless browser with full JavaScript rendering. Strips nav/header/footer by default. Returns structured data: title, URL, markdown content, meta tags, timing. Use this instead of WebFetch when you need JS-rendered content or clean markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to extract content from
delayNoExtra milliseconds to wait after load for async content (default: 0)
formatNoOutput format (default: markdown)markdown
schemaNoOptional. Extract structured fields instead of markdown. An object mapping field name -> CSS selector. Suffix a selector with [] to return all matches as a list, and with @attr to return an attribute instead of text. e.g. {"title":"h1","prices":".price[]","links":"a[]@href"}. When given, returns {url, data:{...}, elapsed_ms}.
stealthNoEnable anti-detection mode
selectorNoCSS selector to wait for before extracting
main_onlyNoStrip nav/header/footer/sidebar (default: true)
max_charsNoTruncate content to N characters (0 = unlimited, default: 0)
wait_untilNoWhen to consider page loaded (default: load)load
Behavior4/5

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

Discloses behavioral traits like stripping nav/header/footer by default and returning structured data (title, URL, markdown, meta, timing). No annotations provided, so description carries the burden; it adequately covers key behaviors.

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?

Two focused sentences that front-load the action and provide value without fluff. Slightly more detail on use case could be added without losing conciseness.

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?

Given 9 parameters, no output schema, and no annotations, the description provides a clear overview and return structure, though it could mention edge cases or limitations of the schema parameter.

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 has 100% coverage, so baseline is 3. Description adds some context (default stripping, return structure) but doesn't significantly enhance parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool extracts clean markdown from a web page using a headless browser with JS rendering, and distinguishes from sibling tools (WebFetch) by specifying when to use it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using this tool over WebFetch when JS-rendered content or clean markdown is needed, providing good context for selection, but lacks explicit 'when not to use' for other siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KultMember6Banger/kloakt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server