Skip to main content
Glama

page_to_markdown

Fetch any URL and return clean Markdown. Strips scripts, styles, and HTML tags; preserves headings, links, bold/italic, lists. Useful for reading docs, news, or competitor pages into an LLM context. Deterministic and stateless — no LLM, no API key. 15s timeout, 50KB default output cap.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttp:// or https:// URL to fetch
max_lengthNoMax characters to return (content truncated beyond this)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses what is stripped, what is preserved, that the operation is deterministic and stateless with no API key, and the 15s timeout and 50KB cap. It omits failure behavior and how non-HTML or JS-rendered pages are handled, which is the remaining gap.

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 tight sentences, front-loaded with the core action and output format before behavior and limits. No filler or repeated content.

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?

For a simple two-parameter fetch-and-convert tool with full schema coverage and no output schema, the description covers output format, transformation rules, determinism, and size/time limits. Error handling and content-type restrictions are the only meaningful omissions.

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 coverage is 100%, so both parameters are already documented, and the description only restates the 50KB default cap that the schema's max_length default already conveys. Baseline 3 is appropriate since the schema does the heavy lifting.

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 return clean Markdown") and immediately details the transformation applied. An agent can distinguish this from every listed sibling, none of which fetch or convert web content.

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 use cases ("reading docs, news, or competitor pages into an LLM context") that tell the agent when this tool applies. It stops short of naming alternatives or exclusions (e.g. binary/PDF URLs, JS-rendered pages), so it is clear context without routing guidance.

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