PageWatch - page-to-data extraction and change monitoring

extract_page

Read-only

Fetch one public static web page and extract structured data from it (text, attr, list, table, price, events, page, links, json). Free tier: 30 calls per day per client. No JavaScript rendering.

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>"
    },
    "name": "extract_page"
  }
}

Input Schema

Name	Required	Description
`all`	No
`url`	Yes
`attr`	No	Attribute name for mode=attr.
`mode`	No	What to extract. Default text for extract_page, page for watch_page.
`paid`	No	true: use the paid endpoint (x402). The result is the payment requirements unless a payment header is sent.
`match`	No	mode=links: regular expression filter.
`fields`	No	mode=list: {"name": "css" or "css@attr"}.
`jsonpath`	No	mode=json: JSONPath-lite such as $.a.b[0].
`sameHost`	No
`selector`	No	CSS selector (required for text, attr, list).
`tableIndex`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes further by disclosing the free-tier rate limit (30 calls/day per client) and the no-JS-rendering limitation, both of which materially affect invocation decisions. It stays silent on failure/empty-extraction behavior, which keeps it out of the top score.

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?

Three short sentences, front-loaded with the core action and tightly packed with the mode list, rate limit and rendering constraint. No sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema and only 64% schema documentation, the description covers the essentials but leaves gaps: several extraction modes (table, events, price, json) are named without clarifying their behavior, and the paid/x402 path is not explained beyond what the schema says.

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

Parameters3/5

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

Schema coverage is 64% and the schema already documents the enum values, selector requirements, match, jsonpath and paid behavior. The description's mode list largely restates the enum and adds nothing about all, sameHost, tableIndex, or how fields/tableIndex interact. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('fetch') and resource ('one public static web page') plus the extraction outcome, and the word 'static' plus the enumerated modes signals a one-shot scrape. It does not explicitly name watch_page, which is the closest sibling, so differentiation from it is left to the agent.

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

Usage Guidelines3/5

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

It states useful operating constraints ('no JavaScript rendering', 30 free calls/day) that imply when this tool fits, but never says when to prefer watch_page or get_changes instead, nor what to do when the page requires JS.

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

All PageWatch - page-to-data extraction and change monitoring tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?