Skip to main content
Glama

map

List URLs on a website from sitemap.xml and start-page links, returning up to 5,000 same-host URLs without fetching each page.

Instructions

List URLs on a website (sitemap.xml first, then links on the start page).

Returns up to limit URLs (maximum 5000) on the same host, without fetching each page.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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 substantive behavior: a two-phase source order (sitemap.xml, then start-page links), a same-host restriction, a 5000 cap, and the fact that individual pages are not fetched. It omits failure behavior (e.g., when no sitemap exists), permission/auth expectations, and the exact return shape beyond "URLs".

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 short sentences, front-loaded with the action and followed by the mechanism and scope constraint. No filler or repetition.

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 is the only source of truth; it covers scope and method but not the return format (array vs object), behavior when the sitemap is missing, or whether redirects/cross-host URLs are dropped. Adequate but with clear gaps for a 2-parameter tool.

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 0%, so the description must compensate for both parameters. It explains that `limit` bounds the returned URL count and adds a 5000 maximum not present in the schema, but `url` is never described as the start page whose links are followed, leaving its role partly implicit.

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?

States a concrete verb+resource ("List URLs on a website") and adds the discovery mechanism (sitemap.xml first, then start-page links). The phrase "without fetching each page" implicitly separates it from the crawl/scrape siblings, though no sibling is named explicitly.

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 only implied: an agent can infer this is the cheap discovery step before fetching pages, but there is no explicit when-to-use, when-not-to-use, or named alternative such as crawl.

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