Skip to main content
Glama
firecrawl

firecrawl-mcp-server

firecrawl_map

Read-only

Discover all indexed URLs on a website. Use the search parameter to find specific pages when scrape returns empty or incomplete results.

Instructions

Map a website to discover all indexed URLs on the site.

Best for: Discovering URLs on a website before deciding what to scrape; finding specific sections or pages within a large site; locating the correct page when scrape returns empty or incomplete results. Not recommended for: When you already know which specific URL you need (use scrape); when you need the content of the pages (use scrape after mapping). Common mistakes: Using crawl to discover URLs instead of map; jumping straight to firecrawl_agent when scrape fails instead of using map first to find the right page.

IMPORTANT - Use map before agent: If firecrawl_scrape returns empty, minimal, or irrelevant content, use firecrawl_map with the search parameter to find the specific page URL containing your target content. This is faster and cheaper than using firecrawl_agent. Only use the agent as a last resort after map+scrape fails.

Prompt Example: "Find the webhook documentation page on this API docs site." Usage Example (discover all URLs):

{
  "name": "firecrawl_map",
  "arguments": {
    "url": "https://example.com"
  }
}

Usage Example (search for specific content - RECOMMENDED when scrape fails):

{
  "name": "firecrawl_map",
  "arguments": {
    "url": "https://docs.example.com/api",
    "search": "webhook events"
  }
}

Returns: Array of URLs found on the site, filtered by search query if provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
limitNo
searchNo
sitemapNo
includeSubdomainsNo
ignoreQueryParametersNo
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so this is a safe read operation. The description adds valuable behavioral context: it is faster and cheaper than firecrawl_agent, and it returns an array of URLs. No contradictions.

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?

The description is well-structured with sections, bold headers, and JSON examples. It is front-loaded with a clear purpose. However, it is slightly verbose, repeating the 'use map before agent' message in multiple places. Still, effective and organized.

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?

Given the tool has 6 parameters, no output schema, but helpful annotations and many siblings, the description covers the core usage well. However, it lacks details on optional parameters like 'limit' and 'sitemap', and the return format is minimally described as 'Array of URLs'. For a tool intended for workflow initiation, more specificity on output and parameter options would be beneficial.

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?

Input schema has 0% description coverage for parameters. The description only demonstrates 'url' and 'search' via examples, but does not explain the other 4 parameters (limit, sitemap, includeSubdomains, ignoreQueryParameters). This leaves the agent without guidance on how to use important optional parameters.

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?

The description clearly defines the tool's purpose: mapping a website to discover URLs. It distinguishes from siblings by explicitly stating it is for URL discovery, not content scraping (firecrawl_scrape) or crawling (firecrawl_crawl). The contrast with firecrawl_agent is also clear.

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?

Excellent usage guidance with explicit 'Best for', 'Not recommended for', 'Common mistakes', and 'IMPORTANT - Use map before agent' sections. It tells when to use the tool (discovering URLs, before scraping) and when not to (when you know the URL, need content). Provides a workflow: map then scrape, agent as last resort.

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/firecrawl/firecrawl-mcp-server'

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