Skip to main content
Glama

webpage_to_markdown

Token-efficient converter that returns ONLY clean Markdown and core metadata from a public webpage or PDF (omits duplicate plain text, links array, and raw HTML). Use when you only need 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": {
      "url": "<url>"
    },
    "name": "webpage_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL of a webpage or PDF to retrieve as Markdown.
max_charsNoMaximum characters returned for Markdown.
force_browserNoStart with browser rendering instead of fast HTTP retrieval.
only_main_contentNoExtract only main article/content (strips nav, footer, aside).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / only_main_content
      Added value: +{
      +  "default": true,
      +  "description": "Extract only main article/content (strips nav, footer, aside).",
      +  "title": "Only Main Content",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / force_browser / description
      Added value: +"Start with browser rendering instead of fast HTTP retrieval."
    • addedInput schema / properties / max_chars / description
      Added value: +"Maximum characters returned for Markdown."
    • addedInput schema / properties / url / description
      Added value: +"Public HTTP or HTTPS URL of a webpage or PDF to retrieve as Markdown."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose what the response omits and that PDFs are supported, which is real behavioral value. It says nothing about how non-public, blocked, or JS-heavy pages behave, no rate limits, and no note on truncation behavior when max_chars caps output.

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 sentences with zero filler: the first front-loads the capability and output contract, the second gives the selection cue. Parenthetical is used efficiently to enumerate exclusions.

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?

With no output schema, the description helpfully characterizes the return payload (Markdown plus core metadata, minus links/HTML/duplicate text), and all four parameters are schema-documented. It falls short only on error/blocked-page behavior and output-size expectations relative to max_chars.

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 every parameter (url, max_chars, force_browser, only_main_content) is already documented in the schema. The description adds no extra parameter guidance such as when to combine force_browser with only_main_content, so the baseline 3 applies.

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 concrete verb and resource ('converter ... returns ONLY clean Markdown and core metadata from a public webpage or PDF') plus a distinguishing scope via the explicit omission list (no duplicate plain text, links array, or raw HTML). An agent can distinguish this from heavier extraction siblings without opening the 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?

'Use when you only need Markdown' gives a positive selection condition tied to output needs, which is genuinely useful routing signal. However it names no alternative tool and states no when-not case (e.g. when you need links, HTML, or JS-rendered pages), leaving the agent to infer siblings like extract_webpage_text.

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.