Skip to main content
Glama
umutc

Scrapedo MCP Server

by umutc

scrape

Fetch web page content by URL and receive raw HTML or markdown. Customize requests with HTTP methods, proxy locations, and screenshot capture for deeper analysis.

Instructions

Basic web scraping without JavaScript rendering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scrape
bodyNoRequest body for POST/PUT
superNoUse residential & mobile proxy network (Super requests)
deviceNoDevice type to emulate
methodNoHTTP method (default: GET)
outputNoOutput format (raw HTML/text or markdown)
geoCodeNoCountry code for proxy location (defaults to "us" when Super and region unspecified)
timeoutNoRequest timeout in milliseconds (5000-120000)
blockAdsNoBlock advertisements
callbackNoWebhook URL for asynchronous delivery (url-encoded)
sessionIdNoSticky session ID (0-1000000) for maintaining the same IP
returnJSONNoReturn Scrape.do JSON payload (required for screenshots/frames data)
screenShotNoCapture default viewport screenshot (requires render & returnJSON)
setCookiesNoSend cookies to the target site (use JSON string or cookie header)
showFramesNoReturn iframe/frame metadata (requires returnJSON)
pureCookiesNoReturn cookies exactly as sent by the target
disableRetryNoDisable automatic retry on failure
extraHeadersNoForward extra upstream headers
retryTimeoutNoRetry timeout in milliseconds (5000-55000)
customHeadersNoLet Scrape.do add default headers automatically
blockResourcesNoBlock images, CSS, fonts to speed up loading
forwardHeadersNoForward client headers to the target site
fullScreenShotNoCapture full-page screenshot (requires render & returnJSON)
playWithBrowserNoJSON-encoded Play-with-Browser action list (array or DSL string)
regionalGeoCodeNoRegional proxy location
disableRedirectionNoDisable following redirects
transparentResponseNoReturn the origin response body directly with no parsing
particularScreenShotNoCapture CSS selector screenshot (selector must be URL-encoded)
showWebsocketRequestsNoReturn websocket request/response logs (requires returnJSON)
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'basic' and 'without JavaScript rendering', but does not explain response formats, default methods, proxy usage, retries, or other behaviors. This is insufficient for a tool with 29 parameters.

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 a single, concise sentence that is front-loaded and wastes no words. It effectively communicates the core purpose in minimal space, earning a perfect score for conciseness.

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

Completeness2/5

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

Given the tool's complexity (29 parameters), lack of output schema, and no annotations, the one-sentence description is inadequate. It fails to explain return values, overall workflow, or what to expect from the tool, leaving the agent with insufficient context for correct invocation.

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 baseline is 3. The description adds no parameter-specific information beyond what the schema already provides, meaning it does not enhance parameter understanding.

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 'Basic web scraping without JavaScript rendering' clearly identifies the tool's function (web scraping) and its scope (no JS rendering). This directly differentiates it from the sibling tool scrape_with_js, making its purpose unambiguous.

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 phrase 'without JavaScript rendering' implies this tool is for static pages when JS execution is not required, contrasting with scrape_with_js. However, it doesn't explicitly mention alternatives or when-not-to-use cases, so it falls short of fully explicit guidance.

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/umutc/scrapedo-mcp-server'

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