Skip to main content
Glama
webscraping-ai

WebScraping-AI MCP Server

Official

webscraping_ai_selected_multiple

Extract content from multiple CSS selectors on a web page. Provide a URL and an array of selectors to retrieve targeted data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the target page.
selectorsYesArray of CSS selectors to extract content for.
timeoutNoMaximum web page retrieval time in ms (20000 by default, maximum is 30000).
jsNoExecute on-page JavaScript using a headless browser (false by default).
js_timeoutNoMaximum JavaScript rendering time in ms (3000 by default).
wait_forNoCSS selector to wait for before returning the page content.
proxyNoType of proxy, datacenter or residential (datacenter by default).datacenter
countryNoCountry of the proxy to use (US by default).
custom_proxyNoYour own proxy URL in "http://user:password@host:port" format.
deviceNoType of device emulation.
error_on_404NoReturn error on 404 HTTP status on the target page (false by default).
error_on_redirectNoReturn error on redirect on the target page (false by default).
js_scriptNoCustom JavaScript code to execute on the target page.

Implementation Reference

  • src/index.js:331-346 (registration)
    Tool 'webscraping_ai_selected_multiple' is registered via server.tool() with a Zod schema (url + selectors array) and a handler that calls client.selectedMultiple().
    server.tool(
      'webscraping_ai_selected_multiple',
      {
        url: z.string().describe('URL of the target page.'),
        selectors: z.array(z.string()).describe('Array of CSS selectors to extract content for.'),
        ...commonOptionsSchema
      },
      async ({ url, selectors, ...options }) => {
        try {
          const result = await client.selectedMultiple(url, selectors, options);
          return createSanitizedResponse(JSON.stringify(result, null, 2), url);
        } catch (error) {
          return createSanitizedResponse(error.message, url, true);
        }
      }
    );
  • The handler function for 'webscraping_ai_selected_multiple' - destructures url, selectors, and options, calls client.selectedMultiple(url, selectors, options), and wraps the result through createSanitizedResponse().
    async ({ url, selectors, ...options }) => {
      try {
        const result = await client.selectedMultiple(url, selectors, options);
        return createSanitizedResponse(JSON.stringify(result, null, 2), url);
      } catch (error) {
        return createSanitizedResponse(error.message, url, true);
      }
    }
  • The client.selectedMultiple() method on WebScrapingAIClient - makes a GET request to '/selected-multiple' endpoint passing url, selectors (array of CSS selectors), and additional options.
    async selectedMultiple(url, selectors, options = {}) {
      return this.request('/selected-multiple', {
        url,
        selectors,
        ...options
      });
    }
  • Input schema for the tool: 'url' (string) and 'selectors' (array of strings) plus common options spread from commonOptionsSchema.
    {
      url: z.string().describe('URL of the target page.'),
      selectors: z.array(z.string()).describe('Array of CSS selectors to extract content for.'),
      ...commonOptionsSchema
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/webscraping-ai/webscraping-ai-mcp-server'

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