Skip to main content
Glama
spider-rs

spider-cloud-mcp

by spider-rs

spider_scrape

Extract content from a single URL. Fetches and processes one page, supporting screenshots and various output formats.

Instructions

Scrape a single page and extract its content. No crawling — just fetches and processes one URL. Supports all output formats and screenshot capture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldNoAllow TLDs
urlYesThe URL to crawl. Can be comma-separated for multiple URLs.
cronNoSchedule crawl
cacheNoHTTP caching. Object: {maxAge, allowStale, period}
proxyNoProxy pool type
binaryNoReturn image as binary instead of base64
budgetNoCrawl budget by path (e.g. {'*':100})
localeNoLocale for content (e.g. 'en-US')
cookiesNoHTTP cookies for SSR authentication
requestNoRequest type. Default: smart
sessionNoPersist HTTP headers and cookies. Default: true
sitemapNoInclude links from sitemaps
timeoutNoOverall request timeout
metadataNoCollect page metadata (title, description, keywords)
sitemapsNoSpecific sitemap URLs to use
timezoneNoTimezone for content
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 config for events (on_find, on_credits_depleted, etc.)
blacklistNoPaths to exclude (supports regex)
block_adsNoBlock advertisements. Default: true
full_pageNoScreenshot full page. Default: true
whitelistNoPaths to include (supports regex)
automationNoWeb automation actions (Click, Fill, Wait, Scroll, etc.)
cdp_paramsNoChrome DevTools Protocol settings
clean_htmlNoClean HTML of unwanted attributes
filter_svgNoFilter SVG elements from markup
screenshotNoEnable screenshot capture
subdomainsNoAllow subdomains
user_agentNoCustom HTTP user agent
fingerprintNoAdvanced fingerprint detection for Chrome. Default: true
readabilityNoUse readability algorithm for content preprocessing
storagelessNoPrevent data storage. Default: true
block_imagesNoBlock image loading
chunking_algNoSegment content: bysentence, bylines, bycharacterlength, bywords
country_codeNoISO country code for proxy (e.g. 'gb')
remote_proxyNoExternal proxy connection URL
event_trackerNoTrack requests, responses, automation
filter_imagesNoFilter image elements from markup
preserve_hostNoPreserve HOST header
proxy_enabledNoEnable premium proxies. Multiplies cost by 1.5x
return_formatNoOutput format. Default: raw
root_selectorNoRoot CSS query selector for content extraction
full_resourcesNoDownload all website resources including assets
respect_robotsNoRespect robots.txt. Default: true
return_cookiesNoReturn HTTP response cookies
return_headersNoReturn HTTP response headers
block_analyticsNoBlock analytics. Default: true
omit_backgroundNoOmit background
redirect_policyNoRedirect policy. Default: Loose
request_timeoutNoHTTP request timeout in ms
exclude_selectorNoCSS selector for content to ignore
external_domainsNoExternal domains to include. Use ['*'] for all
filter_main_onlyNoFilter to main content only. Default: enabled
return_json_dataNoReturn JSON data from SSR scripts
block_stylesheetsNoBlock stylesheets. Default: true
concurrency_limitNoConcurrency limit for slower websites
disable_interceptNoDisable request interception
filter_output_svgNoFilter SVG tags from output
return_page_linksNoReturn links found on each page
run_in_backgroundNoRun in background. Requires storageless=false or webhooks
css_extraction_mapNoCSS/XPath selectors for structured extraction. Shape: { '<url-path>': [{ name, selectors: [...] }] }. '/' matches all paths. Results returned under css_extracted.
request_max_retriesNoMaximum request retries
filter_output_imagesNoFilter images from output
request_redirect_limitNoMaximum redirects to follow
filter_output_main_onlyNoFilter nav, aside, footer from output
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It claims 'No crawling' and 'one URL,' but the schema includes crawl-related parameters (sitemap, subdomains, budget, cron, whitelist, blacklist) and the URL parameter explicitly allows comma-separated multiple URLs, creating a significant misrepresentation. It also fails to mention important behaviors like proxy usage, cost multipliers, data storage, or output details beyond 'all output formats and screenshot.'

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 appropriately short and front-loaded with the main purpose, which is good for conciseness. However, the sentences do not earn their place: 'No crawling' is misleading, and 'Supports all output formats and screenshot capture' merely repeats information already in the schema. It is concise but not effectively informative, striking a balance between brevity and clarity.

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?

This tool has 66 parameters, no output schema, and no annotations, yet the description is only two sentences. It fails to convey essential context like return formats, error handling, cost implications, proxy usage, or even the correct scope (single vs. multiple URLs). The description is grossly inadequate for a tool of this complexity and actively misleads about crawling capabilities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, but the description actively contradicts the schema: it says 'one URL' while the schema states 'Can be comma-separated for multiple URLs,' and it says 'No crawling' while the schema includes crawl-related parameters. The description adds no useful parameter context and instead creates confusion, reducing its helpfulness below the baseline.

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 the tool's function with a specific verb and resource: 'Scrape a single page and extract its content.' It explicitly distinguishes itself from crawling tools by saying 'No crawling — just fetches and processes one URL,' which differentiates it from the sibling 'spider_crawl' tool. This is a clear, unambiguous purpose statement.

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 provides a clear usage context: use this for single-page scraping, not for crawling. The phrase 'No crawling' serves as an explicit exclusion, telling the agent when not to use this tool. However, it does not name the alternative tool (e.g., 'spider_crawl') or provide guidance on multi-page scenarios, so it lacks an explicit alternative recommendation.

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-server'

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