start_crawl
Queue a crawl of a whole site and return a job_id immediately; a worker runs the crawl and the pages count against the account's rolling 30-day page budget. Use it only when the user asks to crawl or audit a site, or names a number of pages; a request to check a single URL, even a homepage, is check_page, and never start a crawl alongside check_page unasked. Pass the max_pages the user named. One crawl per account runs at a time. Poll crawl_status with the job_id until state is "finished", then read the results with issues_summary and query_issues. max_pages defaults to 500 and is capped at 2000 and at the pages remaining in the budget. JavaScript rendering (spa) is not available on the hosted connector.
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>"
},
"name": "start_crawl"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| spa | No | Render JavaScript with a headless browser. Much slower; use only for single-page apps. | |
| url | Yes | Absolute URL to start crawling from, including the scheme. | |
| max_pages | No | Maximum number of pages to fetch. Defaults to 500. Raise it only when the user has asked for a full-site audit and accepts a longer run. | |
| audit_profile | No | Which analyzers to run: "full" (default), "standard", "core", "critical", or "quick". Use "quick" or "critical" when the user wants a fast answer rather than a complete audit. |