Skip to main content
Glama
webscraping-ai

WebScraping-AI MCP Server

Official

Get Page Text

webscraping_ai_text
Read-only

Extract a web page's main content as Markdown, stripping boilerplate while keeping headings, lists, tables, and links for reading or LLM input.

Instructions

Get a web page's main content as Markdown, with boilerplate stripped and structure (headings, lists, tables, links) kept. Best for reading a page or passing it to an LLM. API docs: https://webscraping.ai/docs#text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsNoExecute on-page JavaScript using a headless browser (false by default).
urlYesURL of the target page.
proxyNoType of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page.datacenter
deviceNoType of device emulation.
countryNoCountry of the proxy to use (US by default).
timeoutNoMaximum web page retrieval time in ms (20000 by default, maximum is 30000).
wait_forNoCSS selector to wait for before returning the page content.
js_scriptNoCustom JavaScript code to execute on the target page.
js_timeoutNoMaximum JavaScript rendering time in ms (3000 by default).
text_formatNoFormat of the text response.json
custom_proxyNoYour own proxy URL in "http://user:password@host:port" format.
error_on_404NoReturn error on 404 HTTP status on the target page (false by default).
return_linksNoReturn links from the page body text.
error_on_redirectNoReturn error on redirect on the target page (false by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "gb",
      -  "de",
      -  "it",
      -  "fr",
      -  "ca",
      -  "es",
      -  "ru",
      -  "jp",
      -  "kr",
      -  "in"
      -]New value: +[
      +  "us",
      +  "gb",
      +  "de",
      +  "it",
      +  "fr",
      +  "ca",
      +  "es",
      +  "ru",
      +  "jp",
      +  "kr",
      +  "in",
      +  "hk",
      +  "tr"
      +]
  3. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / proxy / description
      Previous value: -"Type of proxy, datacenter or residential (datacenter by default)."New value: +"Type of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page."
    • changedInput schema / properties / proxy / enum
      Previous value: -[
      -  "datacenter",
      -  "residential"
      -]New value: +[
      +  "datacenter",
      +  "residential",
      +  "stealth"
      +]
  4. Addedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful transformation behavior (boilerplate removal, Markdown structure retention), but says nothing about authentication, rate limits, or how failures surface, which would matter for a network tool.

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?

Two tight sentences plus a docs link. Purpose and output format are front-loaded, and every sentence earns its place with no filler.

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?

No output schema exists, but the description compensates by stating the return format (Markdown with structure preserved). With annotations covering safety and the schema covering all 14 params, the definition is nearly complete; only the option to change response format via text_format goes unmentioned in prose.

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 14 parameters (js, proxy, timeout, text_format, etc.) are already documented in the schema, including enum guidance and defaults. The description adds nothing parameter-specific, so baseline 3 is correct.

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?

States a specific verb and resource ('Get a web page's main content as Markdown') and describes the output shape (boilerplate stripped, structure kept). This implicitly distinguishes it from siblings like webscraping_ai_html or webscraping_ai_data, but it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

'Best for reading a page or passing it to an LLM' implies a use context but gives no when-not-to-use guidance and does not name the sibling tools (question, fields, html, data) that would be the alternatives for other extraction needs.

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