A
licenseNot graded
qualityD
maintenanceZero-signup link-preview API that returns clean metadata (title, description, image, etc.) from any public URL. No API key required.
2
MIT
Link Preview Cache API
Server Details
Same link preview data as link-preview-api, ~1/3 the price via a shared cache.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 46.1% over 42 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- cmondillo/tools
- GitHub Stars
- 0
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The purpose of preview_url is clear.
Naming Consistency4/5
A single tool cannot establish a pattern, but the name preview_url is a clear verb_noun construction that would fit a consistent naming scheme if more tools were added.
Tool Count3/5
One tool is right at the thin edge of acceptability. For a focused 'preview' action it could work, but the server name implies a broader API surface that a single tool does not fulfill.
Completeness2/5
The tool fetches metadata but there is no way to manage cached previews, list them, or delete them. The surface is significantly incomplete for a server named 'Link Preview Cache API'.
Available Tools
1 toolpreview_urlAInspect
Fetch Open Graph / meta metadata for a public URL. Costs $0.003 USDC on Base.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the operation is a read-only fetch and explicitly warns about the $0.003 USDC cost on Base, which is a valuable behavioral detail. It does not discuss failure modes or response format, but the core behavior is transparent.
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 short sentences convey purpose, scope, and cost with no filler. The key information is front-loaded and every word earns its place.
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?
For a simple single-parameter tool with no output schema or annotations, the description gives enough to invoke it correctly: what it fetches, from where, and at what cost. It could be slightly more explicit about the return shape or error behavior, but it is not a significant gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema only lists a required 'url' string with no description. The tool description compensates by specifying that the URL must be a public URL, adding meaningful semantic constraint beyond the schema.
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?
The description uses a specific verb ('Fetch') and identifies the exact resource ('Open Graph / meta metadata for a public URL'). This clearly conveys what the tool does and would distinguish it from siblings if any existed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for a public URL' gives a clear use condition. There are no sibling tools to contrast with, and no exclusions are needed, so the context is sufficiently clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
preview_url
Related MCP Connectors
Pay-per-call Open Graph/link preview metadata for AI agents. $0.01 USDC per call, no signup.
Zero-signup anonymous link-unfurl API. One GET returns clean JSON metadata for any public URL.
Link-preview metadata and clean page-to-Markdown for any public URL. No install.
URL to Markdown or structured JSON (schema.org/OG); renders SPA; batch reads. No signup/key.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceProvides URL metadata extraction (title, description, image, site name) from OpenGraph and meta tags for link previews.-
- FlicenseNot gradedqualityNot gradedmaintenanceURL reality check for AI agents — returns HTTP status, SHA-256 content hash, classification, readability score, title, and wayback-machine fallback when dead, cached 10 minutes at $0.001 per call.-
- AlicenseNot gradedqualityAmaintenanceTurns any URL into structured web intelligence in one call: SEO/OpenGraph metadata, public contacts, tech-stack fingerprinting, Schema.org data, a security-headers audit, and clean AI-ready Markdown. Anti-SSRF hardened by design.10MIT
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.