Skip to main content
Glama

Read web pages

writ_scrape

Read web pages as clean markdown, including multiple URLs or top N items from a listing, even when blocked, JavaScript-rendered, or behind a login.

Instructions

READ PAGE CONTENT NOW — one page, a list of pages, or the top N items of a listing — returned as clean markdown IN THIS CALL (2-10s). This is the tool for 'what does say', 'summarize ', 'the top N posts/products/results of and what's on each', 'fetch these 3 links' — including a page a plain fetch cannot read: blocked or empty (403, bot wall), rendered by JavaScript, or behind the user's sign-in (render_mode, use_residential, persona_id). NOT FOR: collecting a whole site or section into a dataset (writ_crawl_site); clicking, typing, signing in or any action on a page (writ_browser_use).

THREE SHAPES, ONE CALL EACH:

  • url → that page.

  • urls=[...] (≤20) → all of them, fetched in parallel, pages in the order given.

  • url= + top_n=N (≤20) → the listing (listing) AND the N top-ranked item pages it links to (pages, in rank order) — e.g. url='https://news.ycombinator.com/', top_n=3 returns the front page and the 3 top stories' discussion pages. Add include_paths=['item\?id='] when you know the item-link shape; the server otherwise detects it.

Discussion pages keep their comment threads; each comment is tagged [top-level] or [reply · depth N], so 'the top-level comments' is answerable from the text. Long pages are preview-cut at 12000 chars (_truncated); the hint tells you how to fetch a full page. YOU read the markdown — no AI is spent here. Behind a login: persona_id. Bot wall: use_residential=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoA page to read — or, with `top_n`, the LISTING page whose top items to read.
urlsNoKnown pages to read together (max 20), fetched in parallel in one call.
top_nNoWith `url` = a listing/front/search/category page: also read its N top-ranked item pages (the page's link order IS the ranking). One call, parallel.
deviceNoA linked Writ desktop's agent_id (writ_devices): act ON it. Omit to use the desktop this connection chose with writ_devices action='use' (if any).
formatNomarkdown (default): the page's clean main content. html: the RAW HTML as fetched (same egress/persona/render) — for selectors, embedded JSON, anything the cleaned text drops; clipped to preview_chars (default 40000, 0 = whole page). both: html plus the markdown derived from it, one fetch. Single `url` only.
persona_idNoSaved identity to read AS (list them with writ_personas) — for pages behind a login. Forces the identity's own residential exit. A desktop persona ('device:…') reads on its own desktop, from that machine.
render_modeNoauto (default: plain HTTP, browser only if the page needs JS) | http | browser.
include_pathsNoWith top_n: regex(es) the item links match (e.g. 'item\\?id=', '/products/'). Optional — the server detects detail links when omitted.
preview_charsNoCut each page's text to this many characters (default 12000; 0 = full pages).
respect_robotsNoApply robots.txt to the explicitly requested page(s). Default false for scrape; writ_crawl_site defaults true for autonomous discovery.
use_residentialNoFetch through the platform residential network (premium) for a site that blocks datacenter IPs or shows a bot wall. Default off.
residential_countryNoTwo-letter ISO country the residential exit should be in (e.g. 'us', 'fr') — also used by the automatic residential retry on a blocked page. Omit for an automatic exit. Ignored unless the session egresses residential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Discloses behavior well beyond the annotations: 2-10s latency, parallel fetching, 12000-char preview cut with a `_truncated` flag, a `hint` for full retrieval, 'YOU read the markdown — no AI is spent here', and the escalation paths for bot walls (use_residential) and logins (persona_id). Nothing here contradicts readOnlyHint=false/openWorldHint=true; a network egress that may consume premium residential is consistent with non-read-only.

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 and sectioned ('THREE SHAPES, ONE CALL EACH'), so an agent can scan the operative rules quickly. It is nonetheless long and stylistically dense (all-caps opener, heavy em-dash nesting), so a little more restraint would help; every section still carries non-redundant information.

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 and 12 parameters, the description carries the return-shape burden itself, naming `pages`, `listing`, `_truncated`, `hint`, and the comment depth tags, plus failure modes (403/bot wall/JS/empty) and their remedies. Nothing an agent needs to call or interpret this tool 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?

Although schema coverage is 100%, the description adds combinatorial meaning the schema cannot express: the three argument shapes (single url, urls≤20, url+top_n≤20) and exactly what each returns (`pages` in given order, `listing` + ranked `pages`, comment depth tagging). It also clarifies defaults and cross-tool differences for respect_robots, include_paths auto-detection, and residential_country.

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 and resource ('READ PAGE CONTENT') and differentiates immediately from siblings: 'NOT FOR: collecting a whole site ... (writ_crawl_site); clicking, typing, signing in ... (writ_browser_use)'. An agent can pick this tool without opening a sibling 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?

Gives explicit when-to-use phrasing mapped to user intents ('what does <page> say', 'summarize <url>', 'top N posts') plus a dedicated NOT FOR section naming the two alternative tools and their domains. Exclusions and alternatives are both covered.

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