lilbee

Overview Schema Source Related Servers Score Discussions Admin

crawl

Start a non-blocking website crawl and retrieve a task ID for status polling. Set crawl depth, page limits, and choose HTTP or browser rendering.

Instructions

Start a non-blocking crawl; poll via crawl_status(task_id). depth=0 (default) = single URL, N = follow links N levels, null = whole site. render_mode: "http"/"browser".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`depth`	No
`max_pages`	No
`render_mode`	No
`include_subdomains`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv1.0.2Jul 22, 2026
- removedInput schema / properties / depth / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / depth / default
```
Removed value: -null
```
- removedInput schema / properties / depth / title
```
Removed value: -"Depth"
```
- addedInput schema / properties / depth / type
```
Added value: +"integer"
```
- addedInput schema / properties / include_subdomains
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / max_pages / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / max_pages / default
```
Removed value: -null
```
- removedInput schema / properties / max_pages / title
```
Removed value: -"Max Pages"
```
- addedInput schema / properties / max_pages / type
```
Added value: +"integer"
```
- addedInput schema / properties / render_mode / $ref
```
Added value: +"#/$defs/CrawlRenderMode"
```
- removedInput schema / properties / render_mode / anyOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/CrawlRenderMode"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / render_mode / default
```
Removed value: -null
```
- removedInput schema / properties / url / title
```
Removed value: -"Url"
```
- removedInput schema / title
```
Removed value: -"crawlArguments"
```

Changed2 schema fields changedv1.0.1Jun 17, 2026

addedInput schema / $defs

Added value: +{
+  "CrawlRenderMode": {
+    "description": "How a crawl fetches pages. ``http`` uses no browser; ``browser`` runs Chromium with JS.",
+    "enum": [
+      "http",
+      "browser"
+    ],
+    "title": "CrawlRenderMode",
+    "type": "string"
+  }
+}

addedInput schema / properties / render_mode

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CrawlRenderMode"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv1.0.0Jun 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the non-blocking nature, the depth semantics (0, N, null), and render_mode options. However, it omits behavior for max_pages and include_subdomains, and does not mention side effects, resource implications, or how the task_id is returned beyond implying it exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three compact lines with no filler. The main action and polling workflow are front-loaded, followed by parameter semantics. Every sentence adds information.

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 description covers the core workflow and two of five parameters, and an output schema exists so return values need not be described. But for a no-annotation tool with 5 parameters, omitting max_pages and include_subdomains leaves the agent without enough context to use the full tool correctly, and the null-depth note is inconsistent with the schema.

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 0%, so the description must compensate. It adds meaningful semantics for depth (0 default, N levels, null whole site) and restates render_mode options. But url, max_pages, and include_subdomains are left unexplained, and the 'null' depth value conflicts with the schema's integer type, creating ambiguity.

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 opens with a specific action and resource: 'Start a non-blocking crawl.' It also distinguishes itself from the sibling crawl_status by directing the agent to poll via crawl_status(task_id), and from crawl_cancel implicitly by describing the start workflow. The depth and render_mode semantics further clarify what the tool does.

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 gives a clear usage context: use this tool to initiate an asynchronous crawl, then poll with crawl_status. It does not explicitly state when to prefer crawl over search or sync, but it names the companion polling tool and implies the start-then-poll workflow, which is clear context without exclusions.

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