Skip to main content
Glama

microlink

by io.github.pipeworx-io

Get Metadata

get_metadata
Read-onlyIdempotent

Extract metadata from any URL to preview page content. Returns title, description, image, author, publisher, logo, and structured data—useful when you need to understand a webpage without visiting it directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to extract metadata from.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe URL of the webpage
dateNoPublication or modification date
langNoLanguage of the page
logoNoLogo metadata
imageNoPrimary image metadata
titleNoPage title
authorNoAuthor of the page content
publisherNoPublisher of the page
descriptionNoPage description or meta description

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://www.example.com"
+  },
+  {
+    "url": "https://github.com/microlinkhq/sdk"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Author of the page content",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "date": {
+      "description": "Publication or modification date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Page description or meta description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image": {
+      "description": "Primary image metadata",
+      "properties": {
+        "height": {
+          "description": "Image height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Image URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Image width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "lang": {
+      "description": "Language of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logo": {
+      "description": "Logo metadata",
+      "properties": {
+        "height": {
+          "description": "Logo height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Logo URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Logo width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Page title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The URL of the webpage",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "url": "https://www.example.com"
-  },
-  {
-    "url": "https://github.com/microlinkhq/sdk"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "author": {
-      "description": "Author of the page content",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "date": {
-      "description": "Publication or modification date",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "description": {
-      "description": "Page description or meta description",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "image": {
-      "description": "Primary image metadata",
-      "properties": {
-        "height": {
-          "description": "Image height in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Image URL",
-          "type": "string"
-        },
-        "width": {
-          "description": "Image width in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "lang": {
-      "description": "Language of the page",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "logo": {
-      "description": "Logo metadata",
-      "properties": {
-        "height": {
-          "description": "Logo height in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Logo URL",
-          "type": "string"
-        },
-        "width": {
-          "description": "Logo width in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "publisher": {
-      "description": "Publisher of the page",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "title": {
-      "description": "Page title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "description": "The URL of the webpage",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Author of the page content",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "date": {
+      "description": "Publication or modification date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Page description or meta description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image": {
+      "description": "Primary image metadata",
+      "properties": {
+        "height": {
+          "description": "Image height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Image URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Image width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "lang": {
+      "description": "Language of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logo": {
+      "description": "Logo metadata",
+      "properties": {
+        "height": {
+          "description": "Logo height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Logo URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Logo width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Page title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The URL of the webpage",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://www.example.com"
+  },
+  {
+    "url": "https://github.com/microlinkhq/sdk"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive. The description adds useful behavioral context by listing the exact return fields (title, description, image, author, publisher, logo, structured data) and implies no page rendering. No contradictions with annotations.

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 two short sentences, front-loaded with the action, and every part adds value: purpose, output details, and use case. No fluff.

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?

For a simple one-parameter tool with annotations covering safety and an output schema present, the description covers purpose, output fields, and when to use it. Nothing critical is missing.

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?

Schema has 100% coverage for the single 'url' parameter, and the description does not add additional meaning beyond what the schema provides. The baseline of 3 applies, as the description adds no extra parameter semantics.

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 clearly states the tool's function with a specific verb ('Extract metadata') and resource ('from any URL'), and distinguishes it from siblings by listing output fields (title, description, image, etc.) and purpose ('preview page content'). 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context: 'useful when you need to understand a webpage without visiting it directly.' However, it does not explicitly mention alternatives or when not to use the tool, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All microlink toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed usage guidance, but the several query entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) overlap conceptually and require careful reading to select correctly. Notably, ask_pipeworx_beta currently behaves identically to ask_pipeworx, which could cause confusion.

Naming Consistency3/5

Tool names mix verb-first (remember, resolve_entity) and noun-first (entity_profile, deep_research) patterns, with some using prefixes like 'polymarket_' or 'ask_pipeworx'. While all are snake_case and readable, the lack of a single consistent convention makes the set feel less coherent than it could be.

Tool Count3/5

33 tools is on the high end for a single server, though the broad domain (data retrieval, prediction markets, memory, subscriptions, web scraping) justifies much of the sprawl. Still, the count borders on heavy, and some tools could potentially be consolidated (e.g., the ask_pipeworx variants).

Completeness4/5

The toolset provides comprehensive coverage for its core data querying and analysis domain, with lifecycle coverage for memory and subscriptions. Minor gaps exist, such as no generic 'fetch page content' tool despite having get_metadata and take_screenshot, but these do not undermine the primary functionality.

Resources