A
licenseA
qualityA
maintenanceConverts any web page URL into clean Markdown for LLM context (Claude, ChatGPT, etc.) with zero external API calls, running entirely locally.
Last updated
1
798
MIT
webpage-to-pdf
by org.urltopdf
Server Details
Convert any public webpage to a PDF. Single narrow tool, not a bloated PDF toolkit.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.5/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools. The purpose is clearly singular.
Naming Consistency5/5
The single tool name 'convert_url_to_pdf' follows a consistent verb_noun pattern, making it predictable.
Tool Count5/5
One tool is perfectly appropriate for the server's deliberately narrow and focused purpose of converting a single URL to a PDF.
Completeness5/5
The tool fully covers the intended functionality. There are no obvious missing operations given the stated scope of converting a webpage to PDF.
Available Tools
1 toolconvert_url_to_pdfAInspect
Convert a public webpage to a PDF and return a signed download URL (valid for 7 days). Deliberately narrow: one URL in, one PDF out. Requires a urltopdf.org Developer API key.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The public http(s) URL of the page to render. | |
| format | No | Paper size. Default: A4. | |
| landscape | No | Render in landscape orientation. Default: false. | |
| background_graphics | No | Include background colors and images. Default: true. |
Tool Definition Quality
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It states the download URL is signed and valid for 7 days, and that the tool is 'deliberately narrow.' However, it fails to mention authentication mechanism (how the API key is used), error handling for non-public URLs, rate limits, or any side effects. With no annotations, this is insufficient.
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 no redundancy. The first sentence fronts the main action and return value; the second adds constraints and requirements. Every sentence earns its place.
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?
For a tool with 4 parameters and no output schema, the description covers the return type (signed download URL, 7-day validity) and the prerequisite (API key). However, it omits details on error responses, authentication method, and edge cases (e.g., inaccessible URLs, size limits). Adequate but not thorough.
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 input schema has 100% description coverage, so each parameter is already documented. The description does not add extra meaning beyond confirming 'one URL in, one PDF out.' Baseline 3 is appropriate since the schema handles parameter semantics adequately.
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?
Description clearly states the tool converts a public webpage to PDF and returns a signed download URL. It specifies one URL in, one PDF out, making the scope unambiguous. No siblings to distinguish from, but the purpose is well-defined.
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?
The description mentions a prerequisite (urltopdf.org Developer API key), which is useful. However, it does not provide guidance on when to use this tool versus alternatives, nor does it explain context such as ideal use cases or limitations. Usage is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables PDF generation from HTML, text, and Markdown content with customizable formatting options. Provides secure cross-platform PDF creation tools that automatically save to user directories like Downloads, Documents, or Desktop.Last updated441MIT
- Flicense-qualityDmaintenanceConverts HTML files or HTML content to PDF using Puppeteer's browser rendering engine with support for CSS, JavaScript, custom page formats, margins, and header/footer templates.Last updated6
- Alicense-qualityBmaintenanceCaptures full-page screenshots and PDFs from any URL using Chromium rendering, with pay-per-call via x402 micropayments.Last updatedMIT