Skip to main content
Glama
Sign In
webscraping-ai

WebScraping-AI MCP Server

Official
by webscraping-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Selected Element HTML

webscraping_ai_selected
Read-only

Extract the HTML of the first page element that matches a CSS selector from any URL, with optional JavaScript rendering and proxy settings.

Instructions

Get the HTML of the first page element matching a CSS selector. 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.
formatNoResponse format (json or text).json
countryNoCountry of the proxy to use (US by default).
timeoutNoMaximum web page retrieval time in ms (20000 by default, maximum is 30000).
selectorYesCSS selector to extract content for.
wait_forNoCSS selector to wait for before returning the page content.
js_scriptNoCustom JavaScript code to execute on the target page.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only the 'first matching element' scoping behavior and otherwise says nothing about error handling, no-match results, or proxy cost implications (which live in the schema). Adequate but thin given the annotation headroom.

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?

Two short sentences with the core behavior front-loaded and no redundant restatement of the title. The trailing docs URL is compact and arguably useful, though it substitutes for real in-description guidance.

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?

For a 14-parameter tool with no output schema, the description should at least clarify the return shape (HTML string of the matched element) and behavior when nothing matches; it states only 'Get the HTML'. The rich schema compensates for parameter completeness but not for output/edge-case behavior.

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% across all 14 parameters, including enums and defaults, so the schema carries parameter meaning fully. The description adds no parameter-level detail (e.g., how selector interacts with wait_for), so the baseline 3 applies.

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?

States a specific verb and resource ('Get the HTML of the first page element matching a CSS selector') with scope explicitly limited to the first match, which implicitly distinguishes it from sibling webscraping_ai_selected_multiple. It does not name the sibling outright, so it stops short of a 5.

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 guidance on when to use this tool versus webscraping_ai_html (full page HTML), webscraping_ai_text, or webscraping_ai_selected_multiple. The only pointer is an external docs link, leaving the agent to infer selection criteria from the one-line purpose.

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