Skip to main content
Glama
spider-rs

Spider MCP Server

by spider-rs

spider_crawl

Crawl websites to extract content from multiple pages with smart JS rendering. Returns data in markdown, HTML, or text formats up to specified depth and limit.

Instructions

Crawl a website and extract content from multiple pages. Follows links up to the specified depth/limit. Returns content in markdown, HTML, text, or other formats. Powered by Spider — crawls 100K+ pages/sec with smart JS rendering.

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}
delayNoDelay between requests in ms (max 60000). Disables concurrency
depthNoMaximum crawl depth from start URL. Default: 25
limitNoMaximum pages to crawl. 0 for unlimited. Default: 0
proxyNoProxy pool type. residential (x1.2), mobile (x2), isp/datacenter (x1.2)
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
whitelistNoURL path patterns to include (supports regex)
automationNoBrowser automation actions to run before extraction (Click, Fill, Wait, Scroll)
clean_htmlNoStrip unwanted HTML attributes (class, style, etc.)
filter_svgNoRemove SVG elements from markup before processing
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
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
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 the burden. It mentions following links up to depth/limit and JS rendering ('smart JS rendering'), but omits many behavioral details such as caching, robots.txt respect, or concurrency. The description adds some value but is not comprehensive.

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?

Three sentences, front-loaded with purpose. The third sentence is slightly promotional but not excessive. Still efficient for a brief summary.

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 61 parameters, no output schema, the description is too brief. It does not explain output structure, scheduling, proxies, or automation. An agent would lack context for many configuration choices.

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 baseline is 3. The description adds minimal value beyond the schema—only summarizing depth/limit and return_format. It does not clarify default values or parameter interactions.

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 'Crawl a website and extract content from multiple pages' with specific verbs and resources. It mentions depth/limit and return formats, distinguishing it from siblings like spider_scrape or spider_links.

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

Usage Guidelines3/5

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

The description provides a general sense of when to use the tool (crawling multiple pages with depth/limit) but lacks explicit guidance on when not to use it or alternatives. It does not mention siblings like spider_scrape for single pages.

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