olostep-mcp

Create Crawl

create_crawl

Read-only

Crawl a website from a start URL to scrape multiple linked pages, up to a set limit, and return their content or a crawl ID for later retrieval.

Instructions

Use this when you need the content of many pages from one website, such as a docs section or a blog: it follows links from a start URL and scrapes each page it finds, up to max_pages. Waits up to wait_for_completion_seconds (default 45) and returns the pages if the crawl finishes in that time; otherwise returns a crawl_id to pass to get_crawl_results (not get_batch_results). For a known list of URLs use batch_scrape_urls; for one page use scrape_website.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_crawl"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Starting URL for the crawl.
`parser`	No	Optional parser ID for specialized content extraction.
`country`	No	Optional country code for location-specific crawling.
`max_pages`	No	Maximum number of pages to crawl. Set to 1 to scrape only the start URL.
`start_url`	No	Alias for `url`.
`output_format`	No	Format for scraped content. Default: "markdown".	markdown
`wait_for_completion_seconds`	No	Seconds to wait for the crawl to finish and return its pages in this call. 0 returns the crawl_id right away.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.0.21Nov 13, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / follow_links

Removed value: -{
-  "default": true,
-  "description": "Whether to follow links found on pages.",
-  "type": "boolean"
-}

changedInput schema / properties / max_pages / description

Previous value: -"Maximum number of pages to crawl."New value: +"Maximum number of pages to crawl. Set to 1 to scrape only the start URL."

changedInput schema / properties / start_url / description

Previous value: -"Starting URL for the crawl."New value: +"Alias for `url`."

addedInput schema / properties / url

Added value: +{
+  "description": "Starting URL for the crawl.",
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / wait_for_completion_seconds

Added value: +{
+  "default": 45,
+  "description": "Seconds to wait for the crawl to finish and return its pages in this call. 0 returns the crawl_id right away.",
+  "maximum": 300,
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / required
```
Removed value: -[
-  "start_url"
-]
```

Addedv1.0.0Jan 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true); the description adds the crucial async contract that annotations cannot express: the call blocks up to `wait_for_completion_seconds` (default 45) and falls back to returning a crawl_id. It does not mention rate limits, credit cost, or pagination of results, which keeps it short of a 5.

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?

Three sentences, front-loaded with the trigger scenario, then the timeout behavior, then the sibling disambiguation. No filler, and the most decision-relevant facts (scope, async fallback, alternatives) all appear early.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing both possible returns (the pages, or a crawl_id when the wait elapses). For a 7-parameter open-world crawl tool, the combination of trigger conditions, timeout semantics, and follow-up routing leaves nothing an agent needs missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by tying parameters to outcomes rather than just restating them — `max_pages` bounds the discovered page set and `wait_for_completion_seconds` determines whether pages or a crawl_id come back. `parser` and `country` are left entirely to the schema.

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?

States a specific verb and resource ('follows links from a start URL and scrapes each page it finds') plus the scope constraint (one website, up to `max_pages`). It explicitly distinguishes itself from batch_scrape_urls (known URL list) and scrape_website (single page), so an agent can choose without opening other schemas.

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

Usage Guidelines5/5

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

Gives a concrete trigger scenario ('content of many pages from one website, such as a docs section or a blog'), names two alternatives with the conditions that select them, and routes the follow-up call correctly ('pass to get_crawl_results (not get_batch_results)'). When/when-not guidance is complete.

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

Deploy Server