page2md

convert

Fetch a webpage and return it as clean Markdown. Use for any URL an LLM/agent needs to read.

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

Input Schema

Name	Required	Description	Default
`key`	No	page2md key (optional; free tier applies without one)
`url`	Yes	http(s) URL of the page to convert

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden. It discloses that output is clean Markdown but says nothing about failure modes on non-HTML URLs, JS-rendered pages, rate limits, truncation of long pages, or what changes when a paid key is supplied versus free tier — all material for a fetch tool with no structured safety hints.

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 short sentences with zero waste; the core action and output format are front-loaded before the usage hint. Nothing is repeated or padded.

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 a simple two-parameter read tool with full schema coverage, the description covers purpose and return type adequately. It still omits behavioral edges an agent would want — key usage consequences and failure behavior — and offers no differentiation from its siblings.

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 both the url and optional key parameters are already documented in the schema. The description adds no syntax, format, or behavioral detail about either parameter (e.g., what the key unlocks beyond 'free tier applies'), so the baseline 3 applies.

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?

States a specific verb+resource+output format: 'Fetch a webpage and return it as clean Markdown.' An agent immediately knows the action and the return type. It does not differentiate from the sibling convert_raw, which presumably returns unprocessed content, so it stops short of a 5.

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?

The phrase 'Use for any URL an LLM/agent needs to read' implies a usage context but gives no explicit when-not conditions and never names the sibling alternative convert_raw (likely the choice for raw HTML). The agent must infer the selection rule.

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

All page2md 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.