Unstuck

Read web page

read_page

Read-onlyIdempotent

Fetch any URL and get the page's main content as clean markdown. Renders JavaScript in a real browser, so it works on modern sites where a plain fetch returns nothing. Use to read articles, docs, product pages or search results. Price: $0.005 per successful call; failed calls are free. Free to try: a few calls a day without a key.

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": "read_page"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The http(s) URL of the web page to read.
`api_key`	No	Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.

Output Schema

Name	Required	Description
`url`	Yes	Page URL after redirects.
`lang`	Yes	Page language, if declared.
`title`	Yes	Page or article title.
`byline`	Yes	Author line, if found.
`markdown`	Yes	The readable content as markdown.
`site_name`	Yes	Site name, if found.
`truncated`	Yes	True if the markdown was cut at the size limit.
`extraction`	Yes	article = main content detected; body = whole page text.
`balance_usd`	Yes	Remaining prepaid balance, USD.
`charged_usd`	Yes	Amount charged for this call, USD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.",
+  "maxLength": 200,
+  "type": "string"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description adds real behavioral context beyond them: JavaScript is rendered in a real browser, so results differ from a plain fetch, plus the cost model ($0.005 per successful call, failures free) and an unauthenticated free tier. These are operational facts an agent cannot infer from structured fields.

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?

Four short sentences, each earning its place: capability, differentiator, use cases, cost/free tier. The core capability is front-loaded and nothing is redundant with the schema or annotations.

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?

An output schema exists, so return-format detail is unnecessary, and the description covers the remaining agent-relevant unknowns: rendering behavior, cost, and authentication/free-try mechanics. Nothing needed to call it correctly is missing.

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 description coverage is 100% and both parameters (url, api_key) are documented in the schema itself, so the description adds nothing parameter-specific. Per the baseline rule for high coverage, a 3 is appropriate.

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 ('Fetch any URL and get the page's main content as clean markdown') and immediately differentiates from sibling readers by noting JS rendering in a real browser. An agent can distinguish it from screenshot, pdf_to_text, or web_search without opening any schema.

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?

Gives concrete usage contexts ('read articles, docs, product pages or search results') and implicitly scopes it to modern JS-heavy sites where a plain fetch fails. It does not explicitly name when to prefer a sibling like web_search or screenshot instead, so it stops short of full when-not guidance.

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

All Unstuck 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?