Skip to main content
Glama

Get page text

get_page_text
Read-only

Scrape a URL using ScrapingBee and return the page content in Markdown or Text format.

Scope: one URL per call, with the result returned into the conversation. For many URLs, a whole site, output written to a file or directory, resumable jobs, or a scheduled re-run, use the ScrapingBee CLI instead — scrapingbee scrape --input-file urls.txt --output-dir results, scrapingbee crawl URL --save-pattern ..., scrapingbee schedule --every. This server has no batch, crawl, file-output or scheduling equivalent.

Docs: https://www.scrapingbee.com/documentation/remote-mcp/

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the page to scrape.
waitNoMilliseconds to wait after page load (0–35000).
deviceNodesktop (default) or mobile.desktop
cookiesNoSemicolon-separated cookies to send to the target.
timeoutNoRequest timeout in milliseconds (1000–140000, default 140000).
ai_queryNoNatural-language question for AI extraction.
max_costNoOptional credit ceiling for auto_mode (integer >= 1). The request will not escalate to a configuration costing more than this many credits. 0 means no ceiling. Ignored unless auto_mode is True.
wait_forNoCSS or XPath selector to wait for before returning.
auto_modeNoOn by default — ScrapingBee automatically picks the cheapest configuration that successfully fetches the page, escalating proxy strength only as needed (you are charged only for the winning config). To choose a configuration yourself instead, use one of: auto_mode=False for the classic tier (no proxy, cheapest), premium_proxy=True, or stealth_proxy=True — the two proxy flags override auto_mode on their own, so auto_mode=False is only needed for the classic tier. Setting render_js also switches to manual.
render_jsNoWhether to use headless-browser rendering. Omit to use the API default (true). Setting this explicitly switches the request to manual configuration (disables auto_mode).
session_idNoInteger 0–10000000 to reuse an IP for up to 5 minutes.
ai_selectorNoCSS selector to focus AI extraction on part of the page.
js_scenarioNoStringified JSON object of browser interaction instructions.
country_codeNoISO 3166-1 alpha-2 country code (e.g. "fr", "us") to route the request through an IP in that country. Only takes effect when premium_proxy or stealth_proxy is True.
wait_browserNodomcontentloaded (default), load, networkidle0, networkidle2.domcontentloaded
window_widthNoViewport width (default 1920).
custom_googleNoSet to True if the url is a google domain in the following format: <subdomain>.google.<top-level-domain> (Example: translate.google.com, mail.google.com, www.google.co.in etc)
premium_proxyNoManual option: use a premium proxy (middle tier of classic/premium/stealth). Setting this disables auto_mode.
stealth_proxyNoManual option: use a stealth proxy (strongest tier of classic/premium/stealth). Setting this disables auto_mode.
window_heightNoViewport height (default 1080).
block_resourcesNoBlock images/CSS to speed up rendering.
return_page_textNoWhether to return the page content in Text format.
return_page_markdownNoWhether to return the page content in Markdown format.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description is consistent with that. Beyond the annotations it adds genuinely useful behavior: results land in the conversation rather than a file, there is no persistence, resumability, or scheduling, and a docs link is provided. It does not mention credit cost implications or any auth requirement, which leaves some operational context uncovered for a scraper.

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 in sentence one, then scope, then the escape hatch, then docs. Every section earns its place and the negative-scope sentence carries real information. Slightly dense due to the inline CLI command list, but nothing is wasted.

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 23-parameter scraper with an output schema and readOnly annotations, the description supplies the missing pieces an agent needs: single-URL scope, in-conversation output, and the absence of batch/crawl/schedule capabilities. It omits cost/credits guidance and any mention of authentication setup, which would be the remaining gaps.

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 twenty-three parameters are already documented in the schema, including auto_mode, proxy flags, and the return_page_markdown/return_page_text pair. The description only echoes the format choice at a high level and adds no syntax or interaction detail beyond the schema, so baseline 3 applies.

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?

The first sentence states a specific verb (scrape) and resource (a URL) and names the return formats (Markdown or Text), which implicitly separates it from the HTML-returning sibling. It stops short of explicitly naming get_page_html or extract_page_data, so an agent must infer the distinction from the format wording.

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 bounds usage to one URL per call with the result returned into the conversation, then lists the concrete cases that should not use this tool (many URLs, whole site, file output, resumable jobs, scheduled re-runs) and names the alternative CLI with example commands. The statement 'This server has no batch, crawl, file-output or scheduling equivalent' removes any ambiguity about escalation paths within the MCP server.

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.

Resources