Skip to main content
Glama
Sign In
Oxylabs Web API MCP Server

Oxylabs Web API MCP Server

by thevastas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read an offloaded page

read_scraped
Read-only

Retrieve scraped page content stored on disk in chunks. Use the offloaded path and paginate through offsets to access text without loading the entire file.

Instructions

Read a chunk of a scraped page that was offloaded to disk.

Use the path from a scrape result's content_offloaded. Start at offset 0 and keep calling with the returned next_offset until eof is true — and stop as soon as you have what you need rather than reading the whole file by reflex. Returns text plus offset, returned_chars, total_chars, next_offset and eof.

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": {
      "path": "<path>"
    },
    "name": "read_scraped"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath from a result's `content_offloaded.path`.
lengthNoHow many characters to return.
offsetNoCharacter offset to start at.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes further by disclosing the chunked/paginated access pattern, the early-termination recommendation, and the exact response fields (offset, returned_chars, total_chars, next_offset, eof) — real behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight paragraphs: purpose first, then the operating procedure and return shape. Every sentence carries actionable information with no 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?

With an output schema present, the return fields need not be enumerated, yet doing so is harmless and reinforces the paging contract. Combined with a 100%-documented input schema and readOnly annotations, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning above the schema by explaining that `offset` starts at 0 and that the next call should use the returned `next_offset`, i.e. the semantics of the offset/length interplay rather than just their types.

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 (read), resource (scraped page chunk), and qualifier (offloaded to disk) that clearly separates it from scrape/search/extract siblings. An agent can tell this is the paging reader for offloaded content, not a network-fetching tool.

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

Usage Guidelines4/5

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

Explicitly tells the agent where the required `path` comes from ('a scrape result's `content_offloaded`') and gives a concrete loop protocol (start at 0, follow `next_offset` to `eof`). It adds a useful early-stop heuristic. It does not name alternative tools for the case where content was not offloaded, so it falls short of a full when/when-not map.

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