Skip to main content
Glama
mendableai

Firecrawl MCP Server

by mendableai

firecrawl_map

Discover all indexed URLs on a website to identify pages for scraping or locate specific content when scrape results are incomplete.

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
searchNo
sitemapNo
includeSubdomainsNo
limitNo
ignoreQueryParametersNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains the tool's behavior: it discovers URLs, can be used with a search parameter to find specific content, returns an array of URLs, and is faster/cheaper than the agent tool. It mentions practical aspects like handling scrape failures but lacks details on rate limits, authentication, or error handling.

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 clear sections (Best for, Not recommended for, Common mistakes, IMPORTANT, Prompt Example, Usage Examples) and uses bullet points and code blocks effectively. It is appropriately sized for the tool's complexity, though some sections (like the detailed IMPORTANT note) could be more concise. Every sentence adds value.

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

Completeness4/5

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

Given the tool's complexity (6 parameters, no annotations, no output schema), the description is mostly complete. It explains the purpose, usage, and key parameters, and provides examples. However, it lacks details on the return format beyond 'Array of URLs' (e.g., structure, pagination) and does not cover all parameters, leaving some gaps in contextual understanding.

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?

Schema description coverage is 0%, so the description must compensate. It provides meaningful context for the 'url' and 'search' parameters through usage examples and explanations (e.g., using search when scrape fails). However, it does not mention the other four parameters (sitemap, includeSubdomains, limit, ignoreQueryParameters), leaving them undocumented. The description adds value but does not fully cover all 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 states the tool's purpose: 'Map a website to discover all indexed URLs on the site.' It specifies the verb ('map'), resource ('website'), and outcome ('discover all indexed URLs'), and distinguishes it from siblings like scrape, crawl, and agent through explicit comparisons in the 'Best for' and 'Not recommended for' sections.

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?

The description provides explicit guidance on when to use this tool versus alternatives. It includes 'Best for' scenarios (e.g., discovering URLs before scraping), 'Not recommended for' cases (e.g., when you already know the URL), and names specific sibling tools (scrape, agent) as alternatives. The 'IMPORTANT' section further clarifies usage in relation to scrape failures.

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

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