Skip to main content
Glama
Sign In
Markdownify MCP Server

Markdownify MCP Server

by anis-marrouchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

webpage-to-markdown

Convert webpages to Markdown format for easier editing, sharing, and content repurposing. Extract text from any URL to create clean, readable documents.

Instructions

Convert a webpage to 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
urlYesURL of the webpage to convert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.9/5.0
Behavior2/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 of behavioral disclosure. It states the conversion action but lacks details on traits like error handling (e.g., invalid URLs, network issues), performance (e.g., timeouts, size limits), or output specifics (e.g., markdown format quality, included elements). This is a significant gap for a tool with no structured safety hints.

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?

The description is extremely concise—a single, direct sentence with zero wasted words. It's front-loaded with the core action, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (conversion operation), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like what happens on failure, what the markdown output includes, or limitations (e.g., dynamic content handling). For a tool with no structured safety or output info, more context is needed.

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?

The schema description coverage is 100%, with the single parameter 'url' fully documented in the schema. The description adds no additional meaning beyond implying the URL is for a webpage, which is already clear from the schema. This meets the baseline score when the schema does the heavy lifting.

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 clearly states the tool's purpose with a specific verb ('Convert') and resource ('a webpage to markdown'), making it immediately understandable. However, it doesn't distinguish this tool from its siblings (e.g., 'pdf-to-markdown', 'docx-to-markdown'), which all convert different content types to markdown, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites (e.g., URL accessibility), exclusions (e.g., unsupported webpage types), or comparisons to sibling tools like 'bing-search-to-markdown' for web content. This leaves the agent with minimal context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools