Skip to main content
Glama

Stringer CleanExtract

by app.getstringer
OverviewDiscussionsAdmin

Read a web page as clean Markdown

clean_extract

Extract a full page or selected sections from a public URL or raw HTML as clean Markdown, with navigation, scripts and page chrome removed. Use it instead of a raw fetch when a task needs the text of documentation, an article, an RFC or another reference page: in a five-site benchmark the Markdown was 62% fewer estimated tokens than the HTML. Call the free clean_extract_outline first on a long page, then pass only the section ids you need. A call is charged only when it returns usable content; the first 3 usable extraction calls are free, total, then USD 0.05. Uncharged failures name upstream_timeout, upstream_http_error, bot_challenge, js_shell, empty_extraction, or sections_not_found. Recoverable structured data names fallback_used. Every success reports extraction_quality and extraction_content_ratio_band.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNoOptional ids from clean_extract_outline. Return only these sections in document order.
url_or_htmlYesA public HTTP(S) URL or a raw HTML string to convert into Markdown.
max_output_bytesNoOptional maximum UTF-8 byte length of the returned Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sections
      Added value: +{
+  "description": "Optional ids from clean_extract_outline. Return only these sections in document order.",
+  "items": {
+    "pattern": "^s[1-9][0-9]*$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / max_output_bytes
      Added value: +{
+  "description": "Optional maximum UTF-8 byte length of the returned Markdown.",
+  "maximum": 1048576,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / url_or_html / description
      Previous value: -"The public URL or raw HTML string to convert into markdown."New value: +"A public HTTP(S) URL or a raw HTML string to convert into Markdown."
    • addedInput schema / properties / url_or_html / minLength
      Added value: +1
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only carry openWorldHint, so the description carries the behavioral load and does so richly: billing model (charged only on usable content, first 3 free then USD 0.05), enumerated failure codes that are not charged, the fallback_used signal, and the success quality fields. These are non-obvious traits an agent needs to plan cost and retries.

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?

Front-loaded with the core action and the differentiating comparison, and every sentence carries weight (benchmark, sequencing, billing, error taxonomy). The error-code enumeration is dense but is genuinely decision-relevant, so only a small deduction for length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe returns — it does, naming extraction_quality, extraction_content_ratio_band and fallback_used. Combined with failure modes and billing, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so all three parameters are already documented in the schema; the baseline is 3. The description adds only the origin of section ids (from clean_extract_outline) and document-order return, which is useful but marginal over 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?

States a specific verb (extract), resource (full page or selected sections from URL/raw HTML), and output form (clean Markdown with navigation, scripts and chrome removed). Also distinguishes itself from a raw fetch, so an agent can tell it apart from generic retrieval.

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

Usage Guidelines5/5

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

Explicitly says to use it instead of a raw fetch for documentation, articles, RFCs or reference pages, and gives the sequencing rule: call clean_extract_outline first on a long page, then pass only the needed section ids. This is clear when-to-use and how-to-compose guidance referencing the sibling tool.

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

All Stringer CleanExtract toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources