Skip to main content
Glama

SolSignal Web Tools

Web page to Markdown

web_to_markdown
Read-only

Fetch any public web page and return clean Markdown (main article content by default, or the full page). Renders JavaScript-heavy pages in headless Chromium automatically when needed. Returns title, byline, 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": "web_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
modeNo
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare read-only and open-world, so the description carries real weight and delivers: automatic headless-Chromium rendering for JS-heavy pages (a meaningful latency/side-effect signal) and the returned fields (title, byline, markdown). It still omits failure modes, timeouts, and truncation behavior tied to max_chars.

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 short sentences, front-loaded with the core action and default, then capability, then return shape. No wasted wording and no repetition of schema fields.

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 enumerates return fields, and the JS-rendering note covers the main behavioral unknown. The only real hole is the undocumented max_chars parameter and any truncation semantics for a low-coverage 3-param schema.

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 33%, so the description must compensate. It does explain the mode enum semantics ("main article content by default, or the full page"), but max_chars is never mentioned — an agent gets no guidance that it caps output length or what happens on overflow.

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?

The description states a specific verb+resource ("Fetch any public web page and return clean Markdown") and names the return format and default behavior. It implicitly separates itself from pdf_to_text/image_ocr by being web-page-specific, but never names or contrasts a sibling explicitly.

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?

Usage context is implied ("any public web page", article-by-default) but there is no explicit when-to-use versus when-not guidance, no mention of when to prefer pdf_to_text or web_links, and no stated prerequisites for the URL beyond "public http(s)".

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