Read pages by URL
extractFetch supplied URLs and return their page content as Markdown, HTML, or text for reading or processing; use when you already have URLs rather than needing to discover pages.
Instructions
Read pages you have URLs for, as markdown, HTML or text, in a few seconds. It reads, it does not find: URLs come from search, the user or a page. A page behind a login or clicks is browser_open's. provider='max' races every backend, one fetch each: only when the user wants speed over cost. data_apis: its site's vendor APIs, for call_vendor.
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": {
"urls": "<urls>"
},
"name": "extract"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | The URLs to fetch, in the order the documents come back. | |
| format | No | A backend that cannot produce it refuses rather than return another. | |
| provider | No | ||
| data_apis | No | Also list each page's site's vendor data APIs; free, never run. On by default. | |
| configured_only | No | Only data APIs whose credentials are set here. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| handle | Yes | ||
| provider | No | ||
| documents | No | ||
| truncated | No |