Extract structured data from a web page
web_extract_runExtract structured fields from a web page using a CSS selector schema with a base selector and field rules for text, attributes, HTML, or regex.
Instructions
Extract structured fields from a web page using a CSS selector schema. Requires url and schema. schema is required. Example: {"url":"https://example.com/blog","schema":{"name":"posts","baseSelector":"article","fields":[{"name":"title","selector":"h2","type":"text"}]}}.
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>",
"schema": "<schema>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "web_extract_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Required. Web page URL to fetch. | |
| proxy | No | Most expensive proxy tier to use. The page is tried on `datacenter` first and moves up only if it is blocked, stopping at this tier. Default: every tier (`mobile`). | |
| schema | Yes | CSS selector-based JSON extraction schema: baseSelector plus fields. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| waitFor | No | Wait for a CSS selector before extraction. Must be prefixed with "css:" (e.g. css:main). JavaScript wait conditions are not supported. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| maxCredits | No | Most credits this call may cost (2–25). Default 2, which loads about 3.2 MB on the datacenter proxy or 380 KB on residential or mobile. Raise it for heavy pages; you're charged only for what the page uses. | |
| scanFullPage | No | When true, scroll the page to load dynamically appended content. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |