htmldrop
Server Details
Publish HTML, Markdown, PDF, or images as instant shareable links with expiry and passwords.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- vin-spiegel/htmldrop
- GitHub Stars
- 9
- Server Listing
- htmldrop
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 4.4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion or overlap.
A single tool trivially follows its own naming pattern; there is no inconsistency.
The server has a focused purpose but only one tool; while a simple publish action is plausible, a full service would typically include management operations.
The server only supports publishing, with no tools for listing, updating, or deleting published documents, which are significant gaps for a document-sharing service.
Available Tools
1 toolpublish_htmlAInspect
Publish an HTML or markdown artifact (or fetch a remote HTML page) and get a shareable URL. Markdown is rendered into a clean reader page. Useful for sharing reports, dashboards, visualizations, or any document produced by an agent.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | URL of an HTML page to fetch and publish. Provide one of html, markdown, or url. | |
| html | No | HTML content to publish. Provide one of html, markdown, or url. | |
| title | No | Optional page title for the published artifact. | |
| markdown | No | Markdown content to publish; rendered into a styled reader page. Provide one of html, markdown, or url. | |
| password | No | Optional password protection for the artifact. | |
| ttl_days | No | Optional custom TTL in days. Anonymous tier defaults to 7 days. | |
| owner_key | No | Optional owner key for higher limits and ownership. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the burden. It discloses that the tool publishes content and returns a shareable URL, and that markdown is rendered. It does not mention destructive actions, rate limits, or error handling, but the behavior is straightforward for a creation tool. The schema provides additional details like optional password and TTL.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the primary action and outcome, followed by usage examples. No extraneous information; every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 parameters, no output schema, and no annotations, the description covers the main functionality and common use cases. It could elaborate on error scenarios or the format of the returned URL, but it is sufficiently complete for a simple publish tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds meaningful context: it explains that markdown is rendered into a clean reader page and that fetching a remote URL is supported. This goes beyond the schema's property descriptions, justifying an above-baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'publish' and the resources (HTML, markdown, URL) with a specific outcome ('get a shareable URL'). It also clarifies that markdown is rendered into a clean reader page, distinguishing the input types. With no sibling tools, this fully defines the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage context ('useful for sharing reports, dashboards, visualizations, or any document produced by an agent'), which helps an agent understand when to invoke it. However, it lacks explicit when-not-to-use guidance or alternatives, though no siblings exist to compare.
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!
Your Connectors
Sign in to create a connector for this server.