Skip to main content
Glama

map_website

Website URL discovery and sitemap mapper. Discovers and maps internal URLs across a website using robots.txt, XML sitemaps (including nested sitemap indexes), and HTML links, with optional search filtering and subdomain support.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS website URL to map.
searchNoOptional case-insensitive substring filter for discovered URLs.
max_urlsNoMaximum number of URLs returned (1 to 500).
no_cacheNoBypass cache lookup.
include_subdomainsNoInclude URLs on subdomains of the base domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations to rely on, the description does real work by disclosing the discovery mechanism (robots.txt, sitemaps, nested indexes, HTML links) and that discovery can be filtered by search and extended to subdomains. It omits how caching behaves despite shipping a no_cache parameter, and says nothing about crawl scope, rate/politeness limits, or whether the operation is strictly read-only.

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?

Two sentences, no filler, with the resource and mechanism front-loaded. Every clause carries information: the source list and the two optional capabilities.

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?

There is no output schema and no annotations, so the description bears the burden of explaining what comes back, and it never states that the result is a list of URLs, whether ordering or counts are included, or what happens when a site has no sitemap. Inputs are fully covered via schema, so the gap is confined to return-value and failure behavior.

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 url, search, max_urls, no_cache, and include_subdomains are all documented in the schema itself. The description echoes search filtering and subdomain support but adds no semantics beyond the schema (e.g., how no_cache interacts with results, or what max_urls truncation means for completeness). Baseline 3 applies.

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?

The description uses a specific verb and resource ("Discovers and maps internal URLs across a website") and enumerates the exact sources it draws from: robots.txt, XML sitemaps including nested indexes, and HTML links. That is far more than a restatement of the name, and it implicitly separates discovery from the sibling fetch/render/extract tools, though no sibling is named directly.

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: an agent can infer this is the tool for enumerating a site's URLs before fetching content, but there is no explicit "use this when" or "use X instead" routing. No exclusions or prerequisites (e.g., public sites only, crawl scope limits) are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.