Skip to main content
Glama
Sign In
MCP Firecrawl

MCP Firecrawl

by mustafamemon265789-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scrape_url

Scrape any webpage to retrieve clean markdown content with metadata, enabling easy extraction of text and structured data from URLs.

Instructions

Scrape a single webpage and return clean markdown content with metadata

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the webpage to scrape

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 provided, so description must disclose behavior. It specifies output format but lacks details on rate limits, authentication, error handling, or limitations (e.g., JavaScript rendering). Agent has limited insight into operational constraints.

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?

Single sentence, concise and front-loaded with action. No wasted words. Could benefit from slight elaboration on metadata but remains efficient.

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 simple tool (1 param, no output schema, no nested objects), description adequately covers purpose and output. Slight gap on metadata content but not critical for selection.

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 has 100% coverage for the single parameter url, already described as 'The URL of the webpage to scrape'. Description adds no additional meaning beyond the schema, earning baseline 3.

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 verb 'scrape', resource 'single webpage', and output 'clean markdown content with metadata'. This distinguishes from sibling tools: crawl_website (multiple pages) and search_web (search results).

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?

Implied usage for single-page scraping but no explicit when to use or alternatives provided. Does not reference sibling tools or specify when to choose this over crawl_website or search_web.

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