Skip to main content
Glama

web_meta

Fetch metadata from any public URL—title, description, canonical, language, social tags, favicon, RSS feeds, and H1 headings—to inspect or validate a webpage's SEO and sharing data.

Instructions

Fetch a public URL and return its metadata: title, meta description, canonical, language, OpenGraph and Twitter card tags, favicon, RSS feeds, h1s. Public IPs only. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
urlYesurl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

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 well: it discloses a per-successful-call price, the payment protocol (x402), the failure mode without a payment key (402 challenge), and the SSRF-style restriction to public IPs. It omits timeouts, redirect handling, and whether failed fetches are billed, which keeps it below 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?

Three tight sentences: what it returns first, then the eligibility constraint, then the payment mechanics. Every sentence carries information an agent needs, with no filler.

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 enumerating the returned metadata fields, plus it covers the paid-call and 402-challenge behavior that would otherwise surprise an agent. Remaining gaps around error/pagination behavior are minor for a single-URL fetch.

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?

Only one parameter exists and the schema already documents it, so the baseline is 3. The description does add one meaningful constraint on that parameter — the URL must resolve to a public IP — but gives no format hints (scheme requirements, encoding) beyond that.

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?

Uses a specific verb (fetch) plus concrete resource (public URL) and then enumerates exactly what is returned: title, meta description, canonical, language, OG/Twitter tags, favicon, RSS feeds, h1s. An agent can distinguish this from the sibling validators/lookups without opening any schema.

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?

Gives clear qualifying context: the URL must be public (public IPs only) and the call costs 0.002 USDC on Base, with a 402 challenge when no payment key is present. It does not name a sibling alternative or explicitly exclude cases (e.g. when a markdown extraction tool would be preferred), so it stops short of the 5 bar.

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