Skip to main content
Glama
umutc

Scrapedo MCP Server

by umutc

scrape_with_js

Scrape JavaScript-rendered pages by automating a headless browser, enabling extraction of dynamic content with options for proxies, screenshots, and custom load waits.

Instructions

Scrape JavaScript-rendered pages using headless browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scrape
bodyNoRequest body for POST/PUT
superNoUse residential & mobile proxy network (Super requests)
widthNoBrowser viewport width (default: 1920)
deviceNoDevice type to emulate
heightNoBrowser viewport height (default: 1080)
methodNoHTTP method (default: GET)
outputNoOutput format (raw HTML/text or markdown)
renderNoEnable JavaScript rendering (forced true)
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
waitUntilNoWait condition for page load
customWaitNoAdditional wait time in milliseconds
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)
waitSelectorNoCSS selector to wait for before capturing
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)
Behavior1/5

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

With no annotations, the description must disclose behavioral traits, but it only states the core function. There is no mention of headless browser nuances, asynchronous delivery, proxy behavior, retries, screenshots, or dependencies like 'returnJSON'. This is a significant omission for a tool with 35 parameters.

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

Conciseness3/5

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

The description is one sentence and front-loaded, but it is under-specified. While concise, it fails to provide sufficient detail to be useful; it is a terse statement rather than a helpful summary. The brevity is not backed by meaningful content.

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

Completeness1/5

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

Given the tool's complexity (35 parameters, no output schema, no annotations), the description is grossly inadequate. It provides no context about return values, async behavior, limitations, or prerequisites. The agent cannot reasonably understand the tool's full scope from this description alone.

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 parameters are fully documented in the schema. The description adds no extra semantic meaning, but with complete schema coverage, the baseline of 3 is appropriate. No parameter information is missing from the schema itself.

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 description clearly states the tool scrapes JavaScript-rendered pages using a headless browser, which identifies the specific resource and action. It distinguishes from sibling tools like 'scrape' (likely static) and 'scrape_to_markdown' (formatting), though it doesn't explicitly name them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It lacks exclusions or contextual cues, leaving the agent to infer usage from the name alone. The presence of sibling tools like 'scrape' suggests complementary use cases but is never addressed.

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