Skip to main content
Glama

Web page to Markdown

page_markdown
Read-only

Fetch a public web page (robots.txt respected) and return clean Markdown only. HTML only, no JS execution, no PDF. Cheaper than extract_url (0.4 credit). Free 20 calls/day per IP; pass 'Authorization: Bearer ' for prepaid credits.

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_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL

Output Schema

NameRequiredDescriptionDefault
urlYes
titleNo
markdownYes
final_urlYes
fetched_atNo
word_countNo
content_sourceNoWhere the content came from: raw_html = the HTTP response body, no JavaScript executed (current behaviour); rendered = after headless rendering (not offered yet)
markdown_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / content_source
      Added value: +{
      +  "description": "Where the content came from: raw_html = the HTTP response body, no JavaScript executed (current behaviour); rendered = after headless rendering (not offered yet)",
      +  "enum": [
      +    "raw_html",
      +    "rendered"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "fetched_at": {
      +      "type": "string"
      +    },
      +    "final_url": {
      +      "type": "string"
      +    },
      +    "markdown": {
      +      "type": "string"
      +    },
      +    "markdown_truncated": {
      +      "type": "boolean"
      +    },
      +    "title": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "word_count": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "url",
      +    "final_url",
      +    "markdown"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: robots.txt compliance, no JS rendering, no PDF handling, exact credit cost, a 20 calls/day free tier per IP, and the auth mechanism for prepaid credits. These are exactly the operational constraints (rate limits, auth header format, content-type limits) that determine whether a call will succeed.

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?

Three tight sentences, front-loaded with the verb and the output guarantee, then limits, then cost/auth. Every clause carries information an agent would otherwise have to guess.

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?

Output schema exists, so return shape needn't be described; the description instead spends its budget on the constraints that actually gate a call (robots.txt, no JS, no PDF, rate limit, auth). For a single-parameter read tool this covers everything needed to invoke it correctly.

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?

Only one parameter and the schema covers it at 100% with 'Public http(s) URL'. The description reinforces the public/HTML constraint but adds no syntax or format detail beyond the schema, so baseline credit is appropriate rather than special merit.

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 a public web page, return Markdown) and immediately scopes it (HTML only, no JS, no PDF). Names the sibling extract_url and positions itself relative to it on cost, so an agent can tell the two apart without opening either schema.

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 clear usage context: use this when the page is plain HTML and cost matters ('cheaper than extract_url, 0.4 credit'), and the exclusions ('no JS execution, no PDF') tell the agent when to look elsewhere. However, it never states the positive condition under which extract_url is the right call, so the routing rule is inferred rather than explicit.

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.