Skip to main content
Glama
Sign In
MCP Firecrawl

MCP Firecrawl

by mustafamemon265789-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crawl_website

Crawl a website to extract markdown content from multiple pages. Specify a starting URL and limit the number of pages crawled.

Instructions

Crawl multiple pages from a website and return extracted markdown content

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe starting URL to crawl
limitNoMaximum number of pages to crawl (1–100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose key behavioral traits such as rate limits, robots.txt compliance, domain restrictions, or how links are followed. The agent lacks critical information about safety and limitations.

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 a single clear sentence with no filler. It is front-loaded with the core action. However, it could be slightly more structured by separating purpose and output format.

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

Completeness2/5

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

The description lacks completeness for a crawling tool: no mention of scope (e.g., same domain only), depth, handling of dynamic content, or output format details. No output schema exacerbates the gap, and the description fails to provide necessary behavioral context.

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 100%, so the schema already explains the parameters. The description adds general context (multiple pages, markdown output) but does not provide additional parameter-specific semantics beyond what the schema offers.

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?

Description clearly states the tool crawls multiple pages and returns markdown content. It uses a specific verb (crawl) and resource (website), and implicitly distinguishes from siblings: scrape_url (single page) and search_web (search, not crawl).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use: for crawling multiple pages from a website. It does not explicitly exclude single-page use or name alternatives, but the context is clear enough for an agent to infer.

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

Deploy Server

Other Tools