ScrapeUnblocker MCP Server

Official

by ScrapeUnblocker

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List page elements (selector discovery)

list_elements

Read-only

Loads a page and returns a JSON list of notable elements—links, buttons, inputs—with ready-to-use selectors, tags, text, and attributes for building browser automation steps.

Instructions

Load a page through ScrapeUnblocker and return a JSON list of its notable elements (links, inputs, buttons, selects, etc.) with a ready-to-use selector for each, plus tag, text and useful attributes (name, id, type, placeholder, aria_label, href, ...). Read-only and does not interact with the page. This is the discovery half of interactive scraping: call list_elements to find the selectors you need, then pass matching steps to browse_page to click/type/select and capture the resulting HTML.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "list_elements"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The absolute URL whose elements you want to list.
`proxy_country`	No	Optional ISO country code to route through, e.g. 'US'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.5Nov 5, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
Addedv0.2.0Aug 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so safety is covered; the description still adds genuinely new context — loading goes through ScrapeUnblocker, the page is not interacted with, and the return payload shape (selector + tag/text/attributes) is spelled out. It doesn't mention rate limits, caching or failure modes, so not a 5.

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?

The purpose and return shape are front-loaded and the workflow sentence comes last where it belongs. The parenthetical attribute lists are long but each item is informative; a slight tightening of the attribute enumeration would make it a 5.

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

Completeness5/5

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

With no output schema, the description compensates by describing the returned list entries and their fields. Combined with the explicit sequencing advice against browse_page, an agent has everything needed to call it correctly.

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%, so both `url` and `proxy_country` are already documented, including the ISO code constraint. The description adds no syntax or edge-case meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Load a page... return a JSON list') and resource ('notable elements: links, inputs, buttons, selects'), and explicitly frames the tool against its sibling browse_page as 'the discovery half of interactive scraping'. An agent can distinguish it from fetch_html and browse_page immediately.

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

Usage Guidelines5/5

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

Gives an explicit two-step workflow: call list_elements to find selectors, then pass matching `steps` to browse_page to interact. Names the alternative and the condition that selects it, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.