Skip to main content
Glama

Caelara Labs Web Intelligence

url_to_markdown

Convert a web page to clean 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": "url_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about JavaScript rendering, redirects, authentication or paywalls, rate limits, or behavior on very large pages. 'Clean Markdown' is the only behavioral claim and it is unquantified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler, which is efficient. The brevity is close to under-specification rather than padding, so it is not penalized here.

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?

The tool is simple: one required parameter and an implied Markdown return value, which the description does state. However, with no annotations and no output schema, the description should still mention failure modes or content limits; failure to do so leaves an agent unable to predict behavior on blocked or dynamic pages.

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% for the single required parameter, so the baseline applies. The description adds no meaning beyond 'Page URL' — nothing on absolute vs relative URLs, scheme handling, or whether redirects are followed.

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 (convert) and resource (a web page) with a named output format (clean Markdown), so the transform is unambiguous. It does not differentiate against siblings such as html_table_parser or sitemap_crawler, which could plausibly overlap for some inputs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives for structured extraction (e.g. html_table_parser), and no prerequisites such as public accessibility of the page. Usage must be inferred entirely from the tool name.

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