Skip to main content
Glama

Link preview

link_preview
Read-onlyIdempotent

Extract social link preview metadata from any public URL: title, description, canonical URL, Open Graph, Twitter cards, preview image, favicon, theme color, and JSON oEmbed discovery. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "link_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to preview
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add what they can't. It does: cost ($0.001 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the fact that payment settles inside the same call. It doesn't describe failure behavior for non-public or bot-blocked URLs, which is the main remaining unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, capability first, payment mechanics second — correctly front-loaded. The field enumeration is long but each item helps an agent decide whether this tool returns what it needs. Minor density cost from the chain-name list, but nothing is wasted.

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?

There is no output schema, and the description compensates by listing the returned metadata fields, so an agent knows what to expect. Payment handling is fully covered. The gap is behavioral edge cases (redirects, private/unreachable URLs, partial metadata), which would matter for a scraper but are secondary here.

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?

Schema coverage is 100%, so baseline is 3. The description earns the extra point by explaining the two-phase semantics of `payment` — omit it to receive terms, resupply it to complete the purchase — which the schema field text alone does not make obvious. `url` is only constrained to 'public http(s)', matching the schema, with no added detail.

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?

Names a specific verb ('Extract') and resource ('social link preview metadata') and enumerates exactly which fields come back (title, description, canonical URL, OG, Twitter cards, image, favicon, theme color, oEmbed). That field list implicitly separates it from generic extraction siblings, but it never names a concrete alternative such as page_meta or page_extract, so the differentiation is left to inference.

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 x402 flow is spelled out precisely: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. That removes the main ambiguity an agent would hit. It does not say when to pick this over page_meta/page_extract, so it stops short of explicit alternative routing.

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