Skip to main content
Glama

novada_crawl

Read-only

Crawls up to 20 pages from a domain using BFS or DFS to extract content, ideal for documentation ingestion and knowledge base creation.

Instructions

Use when you need content from multiple pages of a site and don't have the URLs yet. Crawls BFS or DFS up to 20 pages, extracts content from each. Use select_paths regex to target specific sections (e.g. "/docs/api/.*").

Best for: Doc site ingestion, competitive content analysis, building knowledge bases from a domain. Not for: A single page (use novada_extract), URL discovery without content extraction (use novada_map — much faster).

Common mistakes:

  • Do NOT set max_pages > 10 for large sites — crawl time scales linearly (~1.4s/page). At max_pages=20, expect 28s minimum.

  • Do NOT use novada_crawl to fetch one page — use novada_extract which is faster and simpler.

  • Use select_paths to restrict to relevant URL patterns before setting max_pages high.

When to use:

  • You need content from multiple pages on one domain (e.g., all /docs/* pages).

  • You need BFS discovery of related content under a path prefix.

Not for:

  • Single-URL extraction — use novada_extract.

  • Finding all URLs on a site without downloading content — use novada_map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
max_pagesYes
strategyYesCrawl traversal order. 'bfs' (default): breadth-first — visits all pages at current depth before going deeper, good for broad discovery. 'dfs': depth-first — follows links deeply before backtracking, good for exploring specific paths.bfs
instructionsNoNatural language hint for which pages to prioritize. E.g. 'only API reference pages', 'skip blog and changelog'. Applied as path-level filtering; semantic filtering is agent-side.
select_pathsNoRegex patterns to restrict crawled URL paths. E.g. ['/docs/.*', '/api/.*'].
exclude_pathsNoRegex patterns for URL paths to skip entirely. E.g. ['/blog/.*', '/changelog/.*'].
formatYesOutput format. 'markdown': human-readable (default). 'json': structured object for programmatic agent use.markdown
renderYesRendering mode. 'auto': uses static, escalates to render on first JS-heavy page detection. 'static': always static. 'render': always render (slower, handles JS sites).auto
limitNoAlias for max_pages — use max_pages for the canonical name. Max 20.
modeNoAlias for strategy — use strategy for the canonical name.
Behavior4/5

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

Description adds behavioral details beyond annotations: crawl time scaling (~1.4s/page), minimum 28s at max_pages=20, and that instructions are path-level filtering. Annotations already indicate safe read (readOnlyHint=true) and open world, so good complement.

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 well-structured with clear sections (Best for, Not for, Common mistakes, When to use). Every sentence adds value, no fluff, front-loaded with key purpose.

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?

Despite no output schema, the description and parameter descriptions for 'format' cover return format. The tool's complexity is addressed with usage advice and performance caveats, making it complete for an agent to use effectively.

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 80%, so schema already documents most parameters. The tool description adds some usage tips (e.g., not to exceed 10 pages for large sites) but doesn't significantly expand parameter semantics beyond 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?

Tool description clearly states it crawls multiple pages from a site using BFS/DFS up to 20 pages. It specifies use cases like doc site ingestion and contrasts with siblings novada_extract and novada_map, making its purpose distinct.

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?

Explicitly provides 'Best for' and 'Not for' sections, including alternatives like novada_extract and novada_map. Lists common mistakes and when to use, offering clear guidance.

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/NovadaLabs/novada-mcp'

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