mcp-server

Crawl Website

alterlab_crawl

Read-onlyIdempotent

Get the content of every page on a site in one job, for RAG, indexing or site-wide export. Use when you need many pages from one domain; for one URL use alterlab_scrape, for a URL list only use alterlab_map. Cost: the alterlab_scrape rate per page crawled, from $0.0002 up to $0.02. Works on JavaScript-heavy and protected sites. Returns a crawl_id immediately; results are available from GET /api/v1/crawl/{crawl_id}. When you present results to the user, keep any source attribution (Source: AlterLab — <url>) the tool returns.

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": "alterlab_crawl"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`formats`	No
`headers`	No
`sitemap`	No	Sitemap handling. Default: include.	include
`timeout`	No
`wait_for`	No
`max_depth`	No	Maximum link depth from the start URL. Default: 3.
`max_pages`	No	Maximum number of pages. Default: 50.
`render_js`	No	Render JavaScript with a headless browser. 'auto' renders only when needed. Default: false.
`use_proxy`	No	Route through a premium proxy. Default: false.
`webhook_url`	No
`sitemap_path`	No
`cost_controls`	No
`respect_robots`	No	Obey robots.txt. Default: true.
`max_concurrency`	No	Maximum parallel page fetches. Default: 10.
`exclude_patterns`	No
`extraction_model`	No
`include_patterns`	No
`extraction_schema`	No	JSON schema for structured extraction. Fields matching this schema are extracted from the page. Example: { "title": "string", "price": "number" }. LLM extraction needs your own LLM API key (OpenAI, Anthropic, OpenRouter, etc.) added in the dashboard BYOK settings; without one the request is rejected with byok_key_required and not charged.
`extraction_profile`	No
`include_subdomains`	No	Include subdomains of the site. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantial context beyond them: per-page pricing with a concrete range, asynchronous job semantics (immediate crawl_id plus retrieval endpoint), JS-heavy/protected-site capability, and a required source-attribution obligation. None of this is derivable from the annotations.

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?

Front-loads the purpose, then routing, then cost, then async behavior and attribution. Every sentence carries distinct operational information with no filler.

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

Completeness4/5

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

For a 21-parameter, nested-schema tool with no output schema, the description covers the critical unknowns: async result retrieval, cost model, JS/proxy capability, and result attribution. It stops short of describing what a crawl result payload contains (page list, per-page fields) or any page-count limits, which would help an agent interpret the eventual response.

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

Parameters2/5

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

Schema coverage is only 43% across 21 parameters, and the description supplies almost no parameter-level meaning — it never explains formats, timeout, wait_for, webhook_url, include/exclude_patterns, cost_controls, extraction_profile, or sitemap_path. Only the cost-per-page note loosely maps to cost_controls, so the description fails to compensate for the coverage gap.

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 ('Get the content of every page on a site in one job') plus concrete use cases (RAG, indexing, site-wide export). It explicitly distinguishes the resource scope from alterlab_scrape (one URL) and alterlab_map (URL list only), so an agent can choose without opening 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 explicit when-to-use guidance ('many pages from one domain') and names both alternatives with the condition that selects each. There are no exclusions left to infer for the scrape/map/crawl decision.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.