Skip to main content
Glama
paulet4a-commits

webdatatools

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

read_url

Fetch one or more article URLs and extract clean, readable Markdown with title, author, date, and body from exact pages you already have.

Instructions

Fetch one or more article/blog/news URLs and return clean, readable article text as Markdown (title, author, date, body). Use this instead of web_search when you already have the exact URL to read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoA single article URL to extract, e.g. https://blog.apify.com/some-post/.
urlsNoMultiple article URLs to extract in one call. Overrides `url` when non-empty.
outputFormatNoWhich body format(s) to return. Markdown is smallest and best for LLM use.markdown
includeImagesNoInclude the main image and image list; turn off for a smaller, text-only result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return payload (title, author, date, body as Markdown), which is genuinely useful. However, it says nothing about failure modes on non-article or JS-heavy pages, rate limits, or partial-batch failure behavior.

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 sentences with zero filler; the capability and output format come first, the sibling routing second. Every clause earns its place.

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

Completeness4/5

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

Covers purpose, output format, and alternative-tool routing, which is what an agent needs to call it correctly. Gaps remain around batch size limits and behavior on unextractable pages, but these are peripheral for a stateless fetch tool.

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%, so all four parameters are already documented in the schema with defaults and the url/urls override rule. The description only adds the informal 'one or more URLs' framing, so the baseline 3 applies.

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 (fetch) and resource (article/blog/news URLs) and specifies the return shape (clean readable text as Markdown with title, author, date, body). It is immediately distinguishable from siblings like web_search or crawl_site_markdown.

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?

Explicitly names the alternative and the selecting condition: 'Use this instead of web_search when you already have the exact URL to read.' Nothing is left to inference about when to pick this tool.

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