Skip to main content
Glama

extract_webpage_text

Token-efficient extractor that returns ONLY clean plain text and core metadata from a public webpage or PDF (omits Markdown formatting, links array, and raw HTML). Use when you only need plain readable text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "extract_webpage_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL of a webpage or PDF to extract plain text from.
max_charsNoMaximum characters returned for content.
force_browserNoStart with browser rendering instead of fast HTTP retrieval.
only_main_contentNoExtract only main article/content (strips nav, footer, aside).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / only_main_content
      Added value: +{
      +  "default": true,
      +  "description": "Extract only main article/content (strips nav, footer, aside).",
      +  "title": "Only Main Content",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / force_browser / description
      Added value: +"Start with browser rendering instead of fast HTTP retrieval."
    • addedInput schema / properties / max_chars / description
      Added value: +"Maximum characters returned for content."
    • addedInput schema / properties / url / description
      Added value: +"Public HTTP or HTTPS URL of a webpage or PDF to extract plain text from."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses useful traits: token-efficient output, plain text plus core metadata, omitted Markdown/links/raw HTML, and public webpage/PDF scope. It does not cover error behavior, authentication/rate limits, or the exact shape of 'core metadata', keeping it short of exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose and differentiation, and contains no wasted wording. Every clause adds useful selection or output-context information.

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?

For a simple read-only extraction tool with rich parameter descriptions, it gives enough context to select and invoke the tool: purpose, output nature, use case, and supported inputs. It has minor gaps around exact return structure and explicit sibling routing, but no output schema means those are not fatal.

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 the schema already documents all four parameters. The description mentions public webpage/PDF support but adds no parameter-specific meaning beyond what the schema provides, making 3 the appropriate baseline.

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?

It states a specific verb and resource: extracts clean plain text and core metadata from a public webpage or PDF. It also explicitly lists omitted artifacts such as Markdown formatting, links arrays, and raw HTML, which distinguishes it from markdown- or HTML-oriented siblings even without naming them.

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?

The description gives a clear use condition: 'Use when you only need plain readable text.' The omission of Markdown, links, and raw HTML implies when other tools may be preferable, but it does not explicitly name alternatives or provide when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.