Skip to main content
Glama
spider-rs

spider-cloud-mcp

by spider-rs

spider_crawl

Crawl a website to extract content from multiple pages, returning data in markdown, HTML, text, or other specified formats.

Instructions

Crawl a website and extract content from multiple pages. Returns page content in the specified format (markdown, HTML, text, etc.). Powered by Spider - the fastest web crawler at 100K+ pages/sec.

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}
delayNoCrawl delay in ms (max 60000). Disables concurrency
depthNoMaximum crawl depth. Default: 25. 0 for no limit.
limitNoMaximum pages to crawl per website. 0 for all pages. Default: 0
proxyNoProxy pool type
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
whitelistNoPaths to include (supports regex)
automationNoWeb automation actions (Click, Fill, Wait, Scroll, etc.)
clean_htmlNoClean HTML of unwanted attributes
filter_svgNoFilter SVG elements from markup
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
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
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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states return format and a promotional speed claim ('fastest web crawler'); it does not mention potential side effects like network cost, premium proxy multipliers, background execution, or external service dependencies. The schema descriptions cover some parameters, but the description itself lacks critical behavioral context.

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?

The description is only two sentences, front-loading the core purpose and output format. It is concise, but the phrase 'Powered by Spider - the fastest web crawler at 100K+ pages/sec' is promotional and adds little actionable information, though it does identify the external provider.

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?

The tool is highly complex (63 parameters, nested objects) and has no output schema. The description provides only a minimal high-level purpose and return format. While the schema descriptions are detailed, the overall description does not explain typical usage patterns, output structure, or how parameters interact, leaving the agent under-oriented for correct invocation and result interpretation.

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% for all 63 parameters, so the schema thoroughly documents each parameter. The tool description adds no additional parameter semantics beyond what the schema already provides, hence the baseline score of 3.

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 action 'Crawl a website' and the scope 'extract content from multiple pages', giving a specific verb and resource. It implies differentiation from siblings like spider_scrape (which likely handles single pages), but does not explicitly name any alternative, so it stops short of full sibling differentiation.

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 'from multiple pages' provides clear context for when to use this tool (multi-page crawling) versus alternatives. However, it does not explicitly mention when not to use it or name specific sibling tools, so it has context but no exclusions.

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