Skip to main content
Glama

Map Site URLs

map
Read-only

Synchronously discover site URLs from sitemaps and a starting page, using substring search filtering, subdomain inclusion, and sitemap modes to build crawl targets.

Instructions

Synchronously discover URLs from a sitemap and the starting page using Firecrawl Local. Map search is URL substring filtering, not semantic search.

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
searchNo
sitemapNoinclude
includeSubdomainsNo

Output Schema

NameRequiredDescriptionDefault
linksYes
partialYes
attemptsYes
providerYes
warningsYes
truncatedYes
artifactIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one genuinely useful trait, 'synchronously', which matters given the presence of crawl_status and crawl_cancel siblings implying async jobs elsewhere. It says nothing about rate limits, size of results, or cost of the open-world crawl.

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 synchronous discovery behavior, then the disambiguation note. No filler.

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?

An output schema exists, so return values need not be described, and the sync-vs-async distinction is covered. However, for a tool with 5 undocumented parameters including a limit cap and a three-value sitemap enum, the definition leaves meaningful gaps an agent would need to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must carry the burden. It clarifies only the `search` parameter (substring filtering) and hints at `sitemap`, leaving `limit`, the sitemap enum values, and `includeSubdomains` entirely unexplained.

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 specific verb and resource: 'discover URLs from a sitemap and the starting page'. It partially differentiates from siblings by noting 'not semantic search', which separates it from the search tool, but it never contrasts itself with crawl or browse.

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?

The 'Map search is URL substring filtering, not semantic search' line implies you should use this rather than semantic search when filtering by URL text, but there is no explicit when-to-use or when-not guidance against crawl/fetch, and no stated prerequisites.

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