Skip to main content
Glama

LinkVet

Get a page's title, description, Open Graph and Twitter tags

page_metadata
Read-onlyIdempotent

Fetch a public page and return its SEO/social metadata: title, meta description, canonical URL, language, robots directive, all Open Graph (og:), Twitter card and article: tags, author, published/modified dates, hreflang alternates and feed links. Use it to build link previews or citations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "page_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety and determinism profile is covered. The description adds one genuinely useful behavioral constraint — 'public page' — implying no authenticated or private pages are reachable. It stays silent on failure modes (non-HTML URLs, missing tags, redirects), which matter for a network fetch.

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?

Verb-and-resource lead, then a compact enumeration of return fields, then a use case. Given there is no output schema, the field list is load-bearing rather than filler, and nothing is repeated or padded.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, so an agent knows exactly what it gets back. Minor gaps remain around error and non-HTML handling for a live network fetch, but the core call contract is complete.

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?

Only one parameter and the schema already documents it at 100% coverage, so the baseline is 3-4. The description contributes the 'public page' framing, narrowing what kind of URL is valid beyond the schema's bare 'Page URL'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Fetch') plus the exact payload returned (title, meta description, canonical, robots, og:*, Twitter, article:*, hreflang, feeds) makes the tool's scope unmistakable. It does not explicitly contrast itself with the sibling read_page, so an agent must infer that this returns metadata rather than page content, but the field enumeration comes close to doing that work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The closing clause 'Use it to build link previews or citations' supplies a positive use case. There is no when-not guidance and no named alternative (e.g. read_page for full body content), so the agent is left to infer the boundary itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources