Skip to main content
Glama

crawl_site

Recursively crawl a website from a given URL, following links up to a maximum depth and page count, and return a short content summary for each page visited.

Instructions

Recursively crawl a website starting from a URL, following links up to a maximum depth and page count. Returns a short content summary for each page visited. Stays on the same domain by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_urlYesPage URL (http/https). Scheme-less input like `example.com` is allowed.
max_depthNoHow many link-hops to follow from the start URL (0 = only the start page).
max_pagesNoHard cap on the total number of pages fetched.
same_domainNoOnly follow links on the start URL's hostname.
formatNoOutput format for each page's content summary.markdown
chars_per_pageNoCharacters of content to include per page.
delay_msNoPoliteness delay between requests, in milliseconds.
renderNoauto=fast static fetch, fall back to headless browser if the page needs JS; static=never use a browser; browser=always render with Playwright (handles SPAs).auto
Behavior3/5

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

With no annotations provided, the description should fully disclose behavior. It mentions returning a short content summary and staying on the same domain, but does not explicitly state that the tool is read-only or discuss rate limiting, authorization, or potential side effects. The lack of such details leaves some ambiguity.

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 extremely concise: only two sentences that convey the essential purpose, behavior, and default constraint. No unnecessary words or redundant repetition.

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?

Given the tool's complexity (8 parameters, no output schema), the description covers the core functionality and default behavior. It does not describe error handling or output structure beyond a 'short content summary,' but the format parameter addresses output style. Slightly lacking in completeness but adequate.

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 coverage is 100%, so the input schema already describes all parameters adequately. The description adds no extra parameter-specific meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 verb 'crawl' and the resource 'website', specifying recursive behavior, depth and page limits, and domain restriction. It differentiates from sibling tools like fetch_page (single page) and extract_by_selector (targeted extraction).

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 implies when to use this tool (multi-page, domain-restricted crawling) but does not explicitly contrast with siblings or state when not to use it. The context of staying on the same domain is helpful but could be more explicit.

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/shadab15github/crawler-mcp'

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