Skip to main content
Glama

scrape

Extract web content as Markdown from any URL. Automatically escalates from static HTML to JavaScript rendering to stealth browser for challenging pages.

Instructions

Extract content from any URL as Markdown. Auto-escalates from fast HTTP to JS rendering to stealth browser. Cost: fast 1 credit, standard 2 credits, thorough 5 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scrape
modeNofast (1 credit, static HTML), standard (2 credits, JS rendering), thorough (5 credits, stealth + CAPTCHA)standard
outputNomarkdown, html, or raw_htmlmarkdown

Implementation Reference

  • Defines the 'scrape' tool's name, description, and input schema (url, mode, output) in the CAPABILITIES array.
    {
      name: "scrape",
      description: "Extract content from any URL as Markdown. Auto-escalates from fast HTTP to JS rendering to stealth browser. Cost: fast 1 credit, standard 2 credits, thorough 5 credits.",
      inputSchema: {
        url: z.string().describe("URL to scrape"),
        mode: z.string().optional().default("standard").describe("fast (1 credit, static HTML), standard (2 credits, JS rendering), thorough (5 credits, stealth + CAPTCHA)"),
        output: z.string().optional().default("markdown").describe("markdown, html, or raw_html"),
      },
    },
  • src/index.ts:247-259 (registration)
    Dynamically registers all capabilities (including 'scrape') as MCP tools via server.registerTool() inside createServer().
    for (const cap of CAPABILITIES) {
      // Cast inputSchema to avoid TS2589 (excessively deep type instantiation from Zod chains)
      server.registerTool(
        cap.name,
        {
          description: cap.description,
          inputSchema: cap.inputSchema as any,
        },
        async (args: any): Promise<CallToolResult> => {
          return callSuprsonic(cap.name, args as Record<string, unknown>);
        },
      );
    }
  • The actual handler for the 'scrape' tool — delegates to callSuprsonic(cap.name, args) which sends a POST to the Suprsonic REST API.
    async (args: any): Promise<CallToolResult> => {
      return callSuprsonic(cap.name, args as Record<string, unknown>);
    },
  • The callSuprsonic helper function that makes HTTP requests to the Suprsonic API for all capabilities including 'scrape'.
    async function callSuprsonic(capability: string, params: Record<string, unknown>): Promise<CallToolResult> {
      if (!API_KEY) {
        return {
          content: [{ type: "text", text: "Error: SUPRSONIC_API_KEY environment variable is not set. Get your key at https://suprsonic.ai/app/apis" }],
          isError: true,
        };
      }
    
      try {
        const resp = await fetch(`${BASE_URL}/v1/agent`, {
          method: "POST",
          headers: {
            "Authorization": `Bearer ${API_KEY}`,
            "Content-Type": "application/json",
          },
          body: JSON.stringify({ capability, params }),
        });
    
        const result = await resp.json() as any;
    
        // Handle non-envelope responses (401, 429, etc. return {"detail": ...})
        if (result.detail && result.success === undefined) {
          const msg = typeof result.detail === "object" ? (result.detail.title || result.detail.detail || JSON.stringify(result.detail)) : String(result.detail);
          return {
            content: [{ type: "text", text: `Error (HTTP ${resp.status}): ${msg}` }],
            isError: true,
          };
        }
    
        if (!result.success) {
          const errMsg = result.error?.detail || result.error?.title || "Request failed";
          return {
            content: [{ type: "text", text: `Error: ${errMsg}` }],
            isError: true,
          };
        }
    
        const text = JSON.stringify(result.data, null, 2);
        const meta = result.metadata
          ? `\n\n[Provider: ${(result.metadata as any).provider_used || "unknown"}, ${(result.metadata as any).response_time_ms || 0}ms, ${result.credits_used || 0} credits]`
          : "";
    
        return {
          content: [{ type: "text", text: text + meta }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Network error: ${err instanceof Error ? err.message : String(err)}` }],
          isError: true,
        };
      }
    }
Behavior4/5

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

Discloses key behaviors: auto-escalation from fast HTTP to JS rendering to stealth browser, plus CAPTCHA handling. Cost structure is transparent. Missing details on rate limits, auth requirements, or error handling, but no annotations exist to contradict.

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

Conciseness5/5

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

Two sentences, front-loaded purpose, no wasted words. Each sentence earns its place.

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?

Covers purpose, escalation, cost, and output format. Missing only minor operational details like rate limits or authentication, which are not required given the 3-parameter schema and no output schema.

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 coverage is 100%, with descriptions for url, mode, and output. Description adds value by explaining the auto-escalation and cost implications not fully captured in schema defaults.

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 action 'Extract content from any URL as Markdown,' with a specific verb and resource. It distinguishes the tool from siblings like screenshot or search by focusing on content extraction.

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?

Provides clear context on when to use each mode via cost levels (fast, standard, thorough) and auto-escalation behavior. However, no explicit exclusions or alternative tools are mentioned.

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/O-mega-Enterprise/suprsonic-mcp'

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