Skip to main content
Glama

bulk-page-to-markdown

Converts up to 20 public web pages to clean markdown in one call. Returns each page's title and markdown body (headings, links, list items, paragraphs; scripts and styles removed), capped at 20,000 characters per page, with a 25-second time limit. Every URL is fetched through a public-internet-only safe fetcher. Use it to pull several docs or articles into one batch instead of making 20 separate calls. Paid only: $0.25 per call via x402 at https://tools.orchardshop.xyz/t/bulk-page-to-markdown.

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": {
      "urls": "<urls>"
    },
    "name": "bulk-page-to-markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYese.g. https://example.com,https://www.iana.org/domains/example

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the whole burden and does it well: per-page output shape (title plus markdown body with scripts/styles removed), a 20,000-character cap, a 25-second wall-clock limit, a public-internet-only fetcher, and a $0.25 x402 payment requirement. The notable remaining gap is failure semantics — nothing says whether one bad or timed-out URL aborts the batch or returns partial results, which matters most for a bulk tool.

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?

Front-loaded with the operation and scope, then constraints, then the selection rule, then the payment requirement in ascending order of invocation relevance. Five sentences, each carrying distinct information, with no restatement of the tool name or filler.

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 a single required parameter, no output schema, and no annotations, the description supplies everything needed for a correct call: input shape, output shape, size and time limits, network restrictions, and cost. Only per-URL error behavior is unstated, which is a minor omission for this complexity level.

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

Parameters4/5

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

Schema coverage is already 100%, but that schema entry is only a bare comma-separated example. The description adds the two facts the schema omits: the list is capped at 20 URLs and each target must be publicly reachable, which changes how an agent builds the argument.

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?

Opens with a specific verb (converts), resource (public web pages), and batch scope (up to 20 in one call). That scope statement is what separates it from the single-page siblings without needing to name them, and an agent can pick correctly on the first read.

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 a concrete selection rule: pull several docs or articles in one batch rather than making 20 separate calls. That implies the single-page alternative exists, but it never names page-to-markdown explicitly, so the routing cue is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources