Spider MCP Server

spider_ai_crawl

Describe your crawl goals in plain English; the AI optimizes the crawl to extract relevant data from any URL.

Instructions

AI-guided website crawling. Describe what you want in plain English and Spider's AI optimizes the crawl automatically. Requires an active AI subscription (https://spider.cloud/ai/pricing).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "prompt": "<prompt>"
    },
    "name": "spider_ai_crawl"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	URL to crawl
`limit`	No	Max pages to crawl
`prompt`	Yes	Natural language instructions (e.g. 'Find all product pages and extract pricing info')
`cookies`	No	HTTP cookies
`request`	No	Request type: http (fast), chrome (JS rendering), smart (auto-detect). Default: smart
`proxy_enabled`	No	Enable premium proxies
`return_format`	No	Output format. Default: raw

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.2Jul 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the AI subscription requirement but lacks details on behavioral aspects like whether the crawl respects robots.txt, rate limits, or how the AI optimization works.

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 concise with two sentences that effectively introduce the tool's key feature and requirement. It is front-loaded but could benefit from a brief structure like a bullet list.

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?

No output schema is provided, and the description does not explain what the tool returns (e.g., scraped content, status, errors). Given the tool's complexity (AI crawl), this is a significant gap.

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 the schema already documents all parameters. The description adds minimal extra meaning beyond restating that AI optimizes based on prompt, not justifying a higher score.

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 it performs AI-guided website crawling with natural language instructions. However, it does not differentiate from sibling tools like spider_ai_scrape or spider_crawl, which also involve crawling.

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 mentions the requirement for an active AI subscription but does not specify when to use this tool versus alternatives such as spider_ai_browser or spider_crawl, nor does it provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.