Skip to main content
Glama
codyde

MCP Firecrawl Server

by codyde

scrape-website

Extract website content in markdown, HTML, or text formats from any URL for data collection and analysis purposes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
formatsNo

Implementation Reference

  • The handler function for the scrape-website tool. It scrapes the website using firecrawl.scrapeUrl, logs debug info, handles errors with Sentry, and returns the scraped content as markdown or other formats in a structured response.
    async ({ url, formats }) => {
      return await Sentry.startSpan(
        { name: "scrape-website" },
        async () => {
          try {
            // Debug input
            console.error('DEBUG: Scraping URL:', url, 'with formats:', formats);
    
            // Add Sentry breadcrumb for debugging
            Sentry.addBreadcrumb({
              category: 'scrape-website',
              message: `Scraping URL: ${url}`,
              data: { formats },
              level: 'info'
            });
    
            // Scrape the website
            const scrapeResult = await firecrawl.scrapeUrl(url, { 
              formats: formats 
            });
    
            // Debug raw response
            console.error('DEBUG: Raw scrape result:', JSON.stringify(scrapeResult, null, 2));
    
            if (!scrapeResult.success) {
              // Capture error in Sentry
              Sentry.captureMessage(`Failed to scrape website: ${scrapeResult.error}`, 'error');
              return {
                content: [{ 
                  type: "text", 
                  text: `Failed to scrape website: ${scrapeResult.error}` 
                }],
                isError: true
              };
            }
    
            // Return the content directly
            return {
              content: [{ 
                type: "text", 
                text: scrapeResult.markdown || scrapeResult.content || 'No content available'
              }]
            };
    
          } catch (error) {
            console.error('DEBUG: Caught error:', error);
            // Capture exception in Sentry
            Sentry.captureException(error);
            return {
              content: [{ 
                type: "text", 
                text: `Error scraping website: ${error.message}` 
              }],
              isError: true
            };
          }
        }
      );
    }
  • Zod input schema defining the parameters for the scrape-website tool: a required URL and optional formats array defaulting to markdown.
    { 
      url: z.string().url(),
      formats: z.array(z.enum(['markdown', 'html', 'text'])).default(['markdown'])
    },
  • src/server.js:62-127 (registration)
    Registration of the scrape-website tool on the MCP server using server.tool(), specifying name, input schema, and handler function.
    server.tool(
      "scrape-website",
      { 
        url: z.string().url(),
        formats: z.array(z.enum(['markdown', 'html', 'text'])).default(['markdown'])
      },
      async ({ url, formats }) => {
        return await Sentry.startSpan(
          { name: "scrape-website" },
          async () => {
            try {
              // Debug input
              console.error('DEBUG: Scraping URL:', url, 'with formats:', formats);
    
              // Add Sentry breadcrumb for debugging
              Sentry.addBreadcrumb({
                category: 'scrape-website',
                message: `Scraping URL: ${url}`,
                data: { formats },
                level: 'info'
              });
    
              // Scrape the website
              const scrapeResult = await firecrawl.scrapeUrl(url, { 
                formats: formats 
              });
    
              // Debug raw response
              console.error('DEBUG: Raw scrape result:', JSON.stringify(scrapeResult, null, 2));
    
              if (!scrapeResult.success) {
                // Capture error in Sentry
                Sentry.captureMessage(`Failed to scrape website: ${scrapeResult.error}`, 'error');
                return {
                  content: [{ 
                    type: "text", 
                    text: `Failed to scrape website: ${scrapeResult.error}` 
                  }],
                  isError: true
                };
              }
    
              // Return the content directly
              return {
                content: [{ 
                  type: "text", 
                  text: scrapeResult.markdown || scrapeResult.content || 'No content available'
                }]
              };
    
            } catch (error) {
              console.error('DEBUG: Caught error:', error);
              // Capture exception in Sentry
              Sentry.captureException(error);
              return {
                content: [{ 
                  type: "text", 
                  text: `Error scraping website: ${error.message}` 
                }],
                isError: true
              };
            }
          }
        );
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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