Skip to main content
Glama
spider-rs

Spider MCP Server

by spider-rs

spider_scrape

Fetch a single URL and extract its content with options for output format, screenshot capture, and various filters. No link following means it processes one page only.

Instructions

Scrape a single page and extract its content. No link following — fetches and processes one URL. Faster and cheaper than crawling. Supports all output formats and optional screenshot capture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldNoFollow top-level domain variations
urlYesThe URL to process. Comma-separate for multiple URLs.
cronNoSchedule recurring crawls
cacheNoHTTP caching. true/false or {maxAge, allowStale, period}
proxyNoProxy pool type. residential (x1.2), mobile (x2), isp/datacenter (x1.2)
binaryNoReturn screenshot as binary instead of base64
budgetNoPage budget per URL path (e.g. {'*': 100, '/blog': 20})
localeNoBrowser locale (e.g. 'en-US')
cookiesNoHTTP cookies for authenticated scraping
requestNoRequest type: http (fast), chrome (JS rendering), smart (auto-detect). Default: smart
sessionNoPersist cookies across requests. Default: true
sitemapNoDiscover pages via sitemap.xml
timeoutNoOverall request timeout in milliseconds
metadataNoCollect page metadata (title, description, keywords)
sitemapsNoSpecific sitemap URLs to use
timezoneNoBrowser timezone
viewportNoDevice viewport settings
wait_forNoChrome-only readiness gate (request: 'chrome' or 'smart'). Object with any of: selector ({selector, timeout}), idle_network ({timeout}), idle_network0, almost_idle_network0, dom ({selector, timeout}), delay ({timeout}), page_navigations (bool). Each timeout is a Rust Duration: { secs, nanos }.
webhooksNoWebhook URLs for async events (on_find, on_credits_depleted)
blacklistNoURL path patterns to exclude (supports regex)
block_adsNoBlock advertisements. Default: true
full_pageNoCapture full scrollable page. Default: true
whitelistNoURL path patterns to include (supports regex)
automationNoBrowser automation actions to run before extraction (Click, Fill, Wait, Scroll)
cdp_paramsNoChrome DevTools Protocol screenshot options (clip, format, quality)
clean_htmlNoStrip unwanted HTML attributes (class, style, etc.)
filter_svgNoRemove SVG elements from markup before processing
screenshotNoEnable screenshot capture
subdomainsNoFollow subdomains
user_agentNoCustom HTTP user agent string
fingerprintNoAdvanced browser fingerprint detection. Default: true
readabilityNoUse readability algorithm for cleaner content extraction
storagelessNoPrevent data storage. Default: true
block_imagesNoBlock images from loading before screenshot
chunking_algNoSegment content: bysentence, bylines, bycharacterlength, bywords
country_codeNoISO country code for geo-located proxy (e.g. 'gb', 'us')
remote_proxyNoExternal proxy URL. Saves 50% on data transfer credits
event_trackerNoTrack detailed request/response events
filter_imagesNoRemove image elements from markup before processing
preserve_hostNoPreserve the HOST header on redirects
proxy_enabledNoEnable premium proxies. Multiplies credit cost by 1.5x
return_formatNoOutput format. Default: raw
root_selectorNoRoot CSS selector to scope extraction (e.g. "#main-content")
full_resourcesNoDownload all resources including images, CSS, JS
respect_robotsNoObey robots.txt rules. Default: true
return_cookiesNoInclude HTTP response cookies
return_headersNoInclude HTTP response headers
block_analyticsNoBlock analytics scripts. Default: true
omit_backgroundNoTransparent background in screenshot
redirect_policyNoHow to handle redirects. Default: Loose
request_timeoutNoPer-request timeout in milliseconds
exclude_selectorNoCSS selector for elements to exclude from output
external_domainsNoExternal domains to follow. Use ['*'] to allow all
filter_main_onlyNoKeep only main content. Default: enabled
return_json_dataNoExtract JSON-LD and structured data from pages
block_stylesheetsNoBlock CSS stylesheets. Default: true
concurrency_limitNoMax concurrent requests to the target site
disable_interceptNoDisable request interception
filter_output_svgNoRemove SVGs from output
return_page_linksNoInclude links found on each page in the response
run_in_backgroundNoRun asynchronously. Requires webhooks or storageless=false
css_extraction_mapNoCSS/XPath selectors for structured extraction. Shape: { '<url-path>': [{ name, selectors: [...] }] }. '/' matches all paths. Results returned under css_extracted.
filter_output_imagesNoRemove images from output
filter_output_main_onlyNoRemove nav, aside, footer from output
Behavior3/5

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

With no annotations, the description carries full burden. It mentions speed and cost relative to crawling and optional screenshot, but lacks details on authentication needs, rate limits, or return format. The description is adequate but not rich enough for a tool with 64 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?

Three sentences with no waste. Front-loaded with the core action and key differentiators. Every sentence adds value.

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

Completeness3/5

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

Given the complexity (64 params, no output schema), the description is sparse. It does not explain return structure or behavior beyond extraction. While the schema covers parameters, the lack of output schema makes the description incomplete for fully informing the agent about results.

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 coverage is 100%, so baseline is 3. The description adds no parameter-specific meaning beyond generic statements like 'Supports all output formats and optional screenshot capture'. It does not enhance the schema's descriptions.

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 clearly states it scrapes a single page and extracts content, with explicit 'No link following' distinguishing it from crawling. It specifies 'Faster and cheaper than crawling' and mentions output formats and screenshots, making the 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 description explicitly says 'No link following' and compares to crawling ('Faster and cheaper than crawling'), guiding the agent to use this for single-page tasks. It could be more explicit about when not to use it (e.g., for multi-page extraction), but the contrast with crawling is effective.

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/spider-rs/spider-cloud-mcp-v2'

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