Skip to main content
Glama
AIMLPM

AIMLPM/markcrawl

crawl_site

Crawl any public website to extract clean content as Markdown or text, stripping navigation and boilerplate. Respects robots.txt and supports JavaScript rendering for SPAs. Outputs structured files for search and analysis.

Instructions

Crawl a website and save extracted content as clean Markdown or plain text.

This tool fetches pages from the given URL, strips navigation, footers,
scripts, and boilerplate, then saves each page as a Markdown file with a
JSONL index (pages.jsonl). It respects robots.txt and uses sitemap-first
discovery when available.

Use this tool when asked to research, read, analyze, or archive a website.
The output_dir from this tool is required by search_pages, read_page,
list_pages, and extract_data.

Typical workflow: crawl_site → list_pages or search_pages → read_page.

Args:
    url: The base URL to crawl (e.g. "https://docs.example.com/"). Only
        public, non-authenticated pages will be fetched.
    output_dir: Directory to save output files. Each crawl creates .md files
        and a pages.jsonl index here. Default: ./crawl_output
    format: Output format — "markdown" (preserves headings, code blocks,
        lists) or "text" (plain text). Default: "markdown".
    max_pages: Maximum number of pages to save. Set to 0 for unlimited.
        Default: 100. Use lower values (10-20) for quick previews.
    include_subdomains: If True, also crawl subdomains (e.g. docs.example.com
        when crawling example.com). Default: False.
    render_js: If True, use a headless Chromium browser to render JavaScript
        before extracting content. Required for React/Vue/Angular sites.
        Slower but necessary for SPAs. Default: False.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
output_dirNo./crawl_output
formatNomarkdown
max_pagesNo
include_subdomainsNo
render_jsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels: it discloses that the tool respects robots.txt, uses sitemap-first discovery, handles subdomains, and offers JS rendering. It also notes that only public, non-authenticated pages are fetched, which is critical behavioral context.

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 well-structured with a concise overview followed by clear parameter explanations in a bullet-like format. It is informative without being verbose, though some default values are repeated from the schema, which could be trimmed slightly.

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?

Given the tool's complexity and the existence of an output schema, the description adequately explains the output (Markdown files and pages.jsonl) and how the output integrates with sibling tools. It covers input, behavior, and integration, making it complete for an AI agent.

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

Parameters5/5

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

The input schema has 0% coverage, so the description must compensate, and it does thoroughly. Each parameter (url, output_dir, format, max_pages, include_subdomains, render_js) has a detailed explanation including meaning, defaults, and usage tips (e.g., 'Use lower values (10-20) for quick previews'). This adds significant meaning beyond 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?

The description clearly states the tool's purpose: crawl a website and save extracted content as clean Markdown or plain text. It specifies the verb 'crawl' and resource 'site', and distinguishes from siblings like search_pages and read_page by mentioning that the output_dir is used by those tools, forming a typical workflow.

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 explicitly says 'Use this tool when asked to research, read, analyze, or archive a website' and provides a typical workflow (crawl_site → list_pages or search_pages → read_page). It does not explicitly state when not to use it or mention alternatives beyond the workflow, but the guidance is clear and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIMLPM/markcrawl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server