Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

web_map

Map a public site into a bounded URL list from sitemaps and seed-page links, with scope, sitemap, and pagination options for crawling.

Instructions

Map a public site. Maps a public site into a bounded, approximate URL list from its sitemaps and the seed page's links. The first request needs url; options are scope, sitemap (include, only, skip), max_urls (1 to 5000, default 1000) and page_size (1 to 500, default 100). Continue with cursor, optionally with page_size; the first page's snapshot lasts 30 minutes.

Input Schema

NameRequiredDescriptionDefault
requestYesMap request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: the output is 'bounded' and 'approximate' (not exhaustive), pagination is cursor-based, and the first page's snapshot expires in 30 minutes (a statefulness detail worth knowing). It omits auth requirements, rate limits, and the failure behavior for non-public or unreachable sites.

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?

Front-loaded and dense; the key constraint (bounded URL list, required url, pagination) comes first. Minor waste in restating 'Map a public site' twice in the opening clause, but otherwise every sentence earns its place.

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

Completeness3/5

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

No output schema exists, and the description does convey the return shape (a bounded list of URLs) and page lifetime, which covers the essentials. It leaves gaps around the `scope` object's fields (query_policy, include/exclude_paths, include_subdomains) and error conditions, which matter for correct invocation.

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?

The description supplies information the schema does not: `url` is required on the first call, `sitemap` has include/only/skip modes (the schema only declares a bare string), `max_urls` is 1-5000 default 1000, `page_size` is 1-500 default 100, and `cursor` drives paging. This is high-value parameter guidance despite the reported 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource + scope: 'Maps a public site into a bounded, approximate URL list from its sitemaps and the seed page's links.' An agent immediately understands this is URL discovery rather than content retrieval. It does not name or distinguish itself from the obvious siblings (web_scrape, web_crawl), so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the pagination flow ('first request needs url... continue with cursor') tells the agent how to operate it, but there is no when-to-use guidance and no comparison against web_scrape/web_crawl for the same host. The agent must infer which sibling to pick.

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

Deploy Server

Other Tools