Skip to main content
Glama
Sign In
webscraping-ai

WebScraping-AI MCP Server

Official
by webscraping-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Multiple Selected Elements HTML

webscraping_ai_selected_multiple
Read-only

Extract HTML content of multiple page elements using a list of CSS selectors from any URL. Specify selectors to retrieve matching elements' HTML in one request.

Instructions

Get the HTML of all page elements matching a list of CSS selectors. API docs: https://webscraping.ai/docs#selected

Input Schema

NameRequiredDescriptionDefault
jsNoExecute on-page JavaScript using a headless browser (false by default).
urlYesURL of the target page.
proxyNoType of proxy: datacenter, residential, or stealth (datacenter by default). Residential and stealth requests cost more than datacenter — see the pricing page.datacenter
deviceNoType of device emulation.
countryNoCountry of the proxy to use (US by default).
timeoutNoMaximum web page retrieval time in ms (20000 by default, maximum is 30000).
wait_forNoCSS selector to wait for before returning the page content.
js_scriptNoCustom JavaScript code to execute on the target page.
selectorsYesArray of CSS selectors to extract content for.
js_timeoutNoMaximum JavaScript rendering time in ms (3000 by default).
custom_proxyNoYour own proxy URL in "http://user:password@host:port" format.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / proxy / description
      Previous value: -"Type of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page."New value: +"Type of proxy: datacenter, residential, or stealth (datacenter by default). Residential and stealth requests cost more than datacenter — see the pricing page."
  2. Changed1 schema field changedv1.2.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "us",
-  "gb",
-  "de",
-  "it",
-  "fr",
-  "ca",
-  "es",
-  "ru",
-  "jp",
-  "kr",
-  "in"
-]New value: +[
+  "us",
+  "gb",
+  "de",
+  "it",
+  "fr",
+  "ca",
+  "es",
+  "ru",
+  "jp",
+  "kr",
+  "in",
+  "hk",
+  "tr"
+]
  4. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / proxy / description
      Previous value: -"Type of proxy, datacenter or residential (datacenter by default)."New value: +"Type of proxy: datacenter, residential, or stealth (datacenter by default). Use residential if the site restricts datacenter traffic, or stealth for the most heavily protected sites with advanced anti-bot detection. Residential and stealth requests cost more than datacenter — see the pricing page."
    • changedInput schema / properties / proxy / enum
      Previous value: -[
-  "datacenter",
-  "residential"
-]New value: +[
+  "datacenter",
+  "residential",
+  "stealth"
+]
  5. Addedv1.0.2

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the core extraction behavior and an API docs link; it does not disclose additional behavioral details such as return shape for multiple matches, handling of missing selectors, or proxy-related costs beyond what the schema already says.

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?

The description is two sentences: one front-loaded statement of what the tool does and one documentation pointer. There is no redundant or low-value text.

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

Completeness3/5

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

The schema fully documents all 13 parameters and annotations cover the read-only/open-world nature, so the description does not need to restate those. However, for a multi-selector extraction tool with no output schema, the description could say more about what the agent receives back or how multiple selector results are structured.

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%, and every one of the 13 parameters is documented in the schema. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: 'Get the HTML of all page elements matching a list of CSS selectors.' This clearly distinguishes the tool from a full-page HTML fetch or a single-selector extraction, though it does not explicitly name the siblings it differs from.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as webscraping_ai_selected or webscraping_ai_html. The phrase 'matching a list of CSS selectors' implies the multiple-selector use case, but the description does not state exclusions or conditions for selecting this tool.

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