Cheap bulk page text: fetch 1-20 URLs and get clean markdown, truncated to a per-page cap. $0.0015 per URL. Price: $0.0015 per URL (1-20); an x402 payment is at least $0.004
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | Pages to fetch | |
| timeout | No | Request timeout in milliseconds | |
| maxChars | No | Per-page content character cap |
Changes observed during successful MCP inspections.
Input schema / properties / urls / examplePrevious value: -[
- "https://example.com/article"
-]New value: +[
+ "https://example.com"
+]Input schema / properties / maxChars / defaultAdded value: +20000Input schema / properties / maxChars / descriptionPrevious value: -"Per-page content character cap (default 20000)"New value: +"Per-page content character cap"Input schema / properties / maxChars / exampleAdded value: +20000Input schema / properties / timeout / defaultAdded value: +10000Input schema / properties / timeout / descriptionPrevious value: -"Per-URL timeout in ms (default 10000)"New value: +"Request timeout in milliseconds"Input schema / properties / urls / descriptionPrevious value: -"URLs to fetch (1-20)"New value: +"Pages to fetch"Input schema / properties / urls / exampleAdded value: +[
+ "https://example.com/article"
+]Input schema / properties / urls / items / descriptionAdded value: +"The URL to process"Input schema / properties / urls / items / formatAdded value: +"uri"Input schema / properties / urls / maxItemsAdded value: +20Input schema / properties / urls / minItemsAdded value: +1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose useful traits: markdown output, per-page truncation, and per-URL pricing with an x402 floor. It omits auth requirements, failure modes, and whether truncation is lossy vs. flagged, so it is only partially transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The first sentence is well front-loaded, but pricing is stated redundantly: '$0.0015 per URL' appears and is then immediately restated as 'Price: $0.0015 per URL (1-20).' That duplicated sentence dilutes otherwise tight prose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-param tool with no output schema and no annotations, the description covers output format and cost but leaves selection among the many fetch/crawl siblings ambiguous. It is adequate but not complete for the surrounding tool set.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds marginal value by implying the per-page cap (maxChars) and the 1-20 URL bound, but says nothing about the timeout parameter beyond what the schema documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (fetch URLs, get clean markdown) with scope (1-20 URLs) and the word 'bulk,' which implicitly distinguishes it from the single-page fetch_webpage siblings. However it never names those siblings, so differentiation is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The '1-20 URLs' and 'bulk' framing implies this is for multi-page fetches rather than single pages, but there is no explicit when-to-use, when-not, or named alternative among fetch_webpage, fetch_webpage_pro, fetch_resilient, or crawl_site.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.