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
url-metadata-api
Server Details
Given a URL, returns title/description/preview-image/site_name from its OpenGraph/meta tags.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- nexus-mcp-infra/url-metadata-api
- GitHub Stars
- 0
- Server Listing
- url-metadata-api
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.7/5.0
Tool DescriptionsA
Average 4.8/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion or overlapping purposes. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
With a single tool, the name follows a clear verb_noun pattern (extract_url_metadata). There are no conflicting conventions to evaluate.
Tool Count3/5
A single tool feels thin for a server, even a focused metadata API. One tool is borderline acceptable, but the server offers no additional capabilities or fallback options.
Completeness5/5
The tool fully covers its stated domain: extracting standard OpenGraph/meta metadata from HTML pages. It explicitly documents limitations (auth, non-HTML), so there are no hidden gaps within its intended scope.
Available Tools
1 toolextract_url_metadataAInspect
Fetch a URL and return its title, description, preview image, and site name, scraped from OpenGraph/meta tags -- the same data a chat app uses to render a link preview card. Rejects non-http(s) URLs and URLs resolving to private/internal addresses. Do NOT use for URLs that require authentication or return non-HTML content (PDFs, images, JSON APIs) -- this tool only parses HTML metadata.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Tool Definition Quality
A4.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
This tool has no annotations, so the description must carry the behavioral disclosure. It does: it mentions rejecting non-http(s) URLs and URLs that resolve to private/internal addresses, and notes it parses only HTML <head> metadata. Those are key behavioral traits. A slight gap is that it does not mention failure behavior (e.g., errors, empty metadata, redirects), but enough is provided for safe use.
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 three succinct sentences moving from purpose to limitations and exclusions. Every sentence is loaded (information-dense) and no words are wasted. It is front-loaded with the operation and output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has a single parameter, no siblings, no annotations, and no output schema. The description covers the core behavior, expected input, output fields, and exclusion criteria. That is fully self-sufficient for an agent to use it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has a single parameter with no description (0% coverage), so the description must compensate. It does: it eventually tells the agent that the URL parameter must be http(s), not private/internal, and must point to HTML content. This is far beyond a bare type/string definition.
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 resource ('a URL'), and clearly states the output: 'title, description, preview image, and site name' scraped from OpenGraph/meta tags. This precisely identifies the tool's function with no ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-not-to-use guidance: 'Do NOT use for URLs that require authentication or return non-HTML content (PDFs, images, JSON APIs)'. It also explains that the tool only parses HTML <head> metadata, which helps an agent decide when to select it.
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
- AlicenseNot gradedqualityCmaintenanceConverts HTML to plain text, extracts hyperlinks, and pulls page metadata (title, description, Open Graph tags) from HTML content.6MIT
- 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.4MIT
- AlicenseNot gradedqualityDmaintenancePaste a URL to see exactly how it renders as a social card on Twitter, LinkedIn, Facebook, and Slack. Generate custom OG images from templates.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.