Skip to main content
Glama
Oxylabs Web API MCP Server

Oxylabs Web API MCP Server

Official

List scrape endpoints

list_scrapers
Read-only

Lists available scrape endpoints and, when given an endpoint name, returns its request-body JSON Schema so you can confirm parameters before running a dedicated scraper.

Instructions

List the scrape endpoints this API implements, or describe one of them.

Not needed to read a URL — scrape does that for any site. Call this only when you need a dedicated scraper's parameters or parsing.

The list is grouped by parser: json_supported endpoints have a dedicated parser (and take the AI parser too), json_supported_only_with_prompt_or_schema ones take only the AI parser, json_not_supported ones return no JSON at all. The batch endpoints listed under /v1/async/scrape/batch/ are used for you: give run_scraper a list instead.

Call this before assuming a dedicated scraper does or does not exist for a site, then call it again with the endpoint name to get the JSON Schema of what that endpoint accepts: types, required, enum values and defaults. That is the authoritative parameter list — more current than any documentation. Run the endpoint itself with run_scraper.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_scrapers"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointNoName a scrape endpoint to get the JSON Schema of its request body instead of the list. Omit it to list what exists.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it explains the three parser buckets and what each implies for JSON output, and discloses that the batch endpoints under /v1/async/scrape/batch/ are handled automatically when a list is passed to `run_scraper`. It also warns that the returned schema is the authoritative parameter source, "more current than any documentation" — a non-obvious trust signal.

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?

Front-loaded with the core purpose and the routing decision, then progressively deeper detail; every paragraph maps to a distinct concern. Slightly long at four blocks, and the parser-taxonomy sentence is dense, but no sentence is filler.

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?

Covers both operating modes, the routing decision versus three siblings, the semantics of the grouped results, and the trust level of the returned schemas. With an output schema present and a single fully documented optional parameter, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning: omitting `endpoint` yields a listing, supplying it returns the JSON Schema of that endpoint's request body, and the schema's content (types, required, enum values, defaults) is spelled out. That is more than the schema field's own text conveys.

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?

Opens with a specific verb and resource: list the scrape endpoints the API implements, or describe one of them. It immediately distinguishes itself from `scrape` ("does that for any site") and later from `run_scraper`, so an agent can place it among its siblings without opening a schema.

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?

Explicitly states when not to call it ("Not needed to read a URL — `scrape` does that") and the exact condition that selects it ("only when you need a dedicated scraper's parameters or parsing"). It further prescribes a two-step pattern — list, then re-call with an endpoint name — and names `run_scraper` as the tool that actually executes.

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