Server Details
Rich Link Previews with One API Call Extract Open Graph, Twitter Cards, favicons, JSON-LD, and structured metadata from any URL. Power beautiful link previews in your app in minutes, not days.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
3 toolsbatch_extract_metadataInspect
Extract metadata from multiple URLs at once (max 10). Use fields to select specific data — include "body" for clean page text, "statusCode" and "contentType" for HTTP response metadata. Response includes redirectChain per URL.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | Array of URLs to extract metadata from | |
| fields | No | Comma-separated fields to return (e.g. "title,body,summary,statusCode,contentType"). Include "body" for clean extracted page text. | |
| timeout | No | Request timeout in milliseconds (default 10000, max 30000). Increase for slow-responding targets. | |
| summary_length | No | Max summary length in characters (default 300, max 2000) |
extract_metadataInspect
Extract metadata (Open Graph, Twitter Cards, favicon, JSON-LD, body text, redirect chain, HTTP status, content type, etc.) from any URL. Use fields to select specific data — include "body" for clean page text (ideal for RAG/embeddings), "statusCode" and "contentType" for HTTP response metadata. Response includes redirectChain showing every HTTP redirect hop.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to extract metadata from | |
| fields | No | Comma-separated fields to return (e.g. "title,body,summary,statusCode,contentType"). Include "body" for clean extracted page text. Available: url,statusCode,contentType,title,description,image,favicon,siteName,type,locale,language,author,publishedDate,modifiedDate,keywords,themeColor,canonical,wordCount,summary,body,redirectChain,twitter,openGraph,jsonLd,responseTime | |
| timeout | No | Request timeout in milliseconds (default 10000, max 30000). Increase for slow-responding targets. | |
| no_cache | No | Bypass cache and fetch fresh metadata | |
| summary_length | No | Max summary length in characters (default 300, max 2000) |
validate_metadataInspect
Validate Open Graph, Twitter Card, and SEO metadata for any URL. Returns a score (0-100), letter grade, list of issues (errors + warnings), and platform-specific readiness for Facebook, Twitter/X, and LinkedIn. Use this to audit link preview quality before sharing.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to validate metadata for | |
| timeout | No | Request timeout in milliseconds (default 10000, max 30000) | |
| no_cache | No | Bypass cache and fetch fresh metadata |
To claim this server, publish 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 verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!