DevX Agent Hub

Link preview / SEO metadata

url_metadata_link_preview

Read-onlyIdempotent

Link preview and SEO metadata for a URL: HTTP status, final URL, response time, title, meta description, OpenGraph and Twitter card tags, canonical, language, favicon, RSS feeds, JSON-LD types and robots directives. $0.001 USDC on Base via x402. Price: $0.001. First call returns the x402 PaymentRequired (no charge); retry with payment in _meta["x402/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": "url_metadata_link_preview"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`x402_payment`	No	Optional. Base64 x402 v2 PaymentPayload, for clients that cannot set params._meta["x402/payment"]. Omit on the first call to get the exact price.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses the two-step x402 payment handshake, that the first call is not charged, and the exact retry mechanism via _meta['x402/payment']. It does not mention error behavior for unreachable URLs or rate limits, but the paid-flow disclosure is the high-value item an agent cannot infer from the annotations.

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?

The output fields are front-loaded in one dense sentence, followed by the price and payment protocol. Minor waste: the price is stated twice ('$0.001 USDC on Base via x402. Price: $0.001.'), which is redundant rather than harmful.

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?

With no output schema, the enumerated field list is exactly what an agent needs to know what comes back, and the payment protocol is spelled out sufficiently to complete a paid call. Little an agent requires to invoke this correctly is missing.

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 50% and the 'url' parameter has no schema description at all, but the description's context makes its meaning obvious (the URL to preview), and it explains the payment-retry path that the x402_payment schema only partially covers. It adds meaningful signal beyond the structured fields.

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?

The description opens with a specific verb+resource ('Link preview and SEO metadata for a URL') and enumerates the exact fields returned (HTTP status, final URL, OpenGraph/Twitter tags, JSON-LD, robots), making the scope unambiguous. It does not differentiate itself from the related sibling web_page_to_markdown, which keeps it from a 5.

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 payment mechanics double as a usage instruction: the first call is free and returns PaymentRequired, then a retry with payment is expected. However, there is no guidance on when to choose this over web_page_to_markdown or other URL tools, and no note about input constraints such as redirects or unsupported schemes.

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

All DevX Agent Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?