Skip to main content
Glama

page-metadata

Fetches any public http(s) page and returns its metadata: title, meta description, canonical URL, favicon URL, all OpenGraph (og:*) properties, and every unique absolute link with its anchor text (up to 500). Blocks localhost and private addresses. Returns JSON with url, final_url, status, title, description, canonical, favicon, og, link_count and links. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/page-metadata.

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
urlYese.g. https://www.iana.org/domains/reserved

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the localhost/private-address block, the 500-link cap, the free-tier limit of 3 calls/day with $0.01 x402 pricing after that, and the exact response field set including final_url (implying redirect following). It stops short of covering timeout, JS-rendering, or error responses, which keeps it from a 5.

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?

Front-loaded with the purpose, then behavior constraints, then the return shape, then cost — a sensible order with no filler sentences. Every clause adds an operational fact the agent needs; the pricing/link sentence is dense but load-bearing.

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 correctly enumerates the returned JSON fields, and it covers rate limits and input restrictions, which is most of what an agent needs for a one-parameter fetch tool. It leaves gaps around error behavior and whether more than 500 links can be retrieved, which matters for a tool that explicitly truncates results.

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% and the single url parameter already carries an example, so the baseline is met by the schema alone. The description adds real meaning beyond it by constraining the parameter to public http(s) targets and excluding private addresses, telling the agent what will be rejected before it calls.

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?

States a specific verb and resource ("Fetches any public http(s) page") and then enumerates exactly what comes back: title, meta description, canonical, favicon, og:* properties, and links with anchor text. That enumeration separates it from siblings like page-to-text and page-to-markdown, which return content rather than metadata, without naming them.

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?

Usage is implied by the scope statement ("any public http(s) page") and the SSRF restriction to non-localhost/non-private addresses, which tells the agent what inputs are valid. However, it never states when to prefer this over the sibling conversion tools (page-to-markdown, page-to-text) or what happens on failure, so the routing decision is left to inference.

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