Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Page title, OG & Twitter card, link-preview metadata (robots.txt respected)

web_meta
Read-only

Get a page title, meta description, canonical URL, Open Graph and Twitter card tags (link previews, SEO checks). Fetch a public page (respects robots.txt) and return title, description, language, canonical URL, H1, Open Graph and Twitter card tags, icons, manifest, alternates and JSON-LD count. Ideal for link previews and SEO checks. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/web/meta

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
urlYesPublic http(s) URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world traits, and the description adds real context beyond them: robots.txt compliance, the restriction to public pages, and a concrete cost of $0.001 USDC per call via x402 v2 on Base, plus a free demo URL. What it omits is failure behavior (what happens on robots-blocked or non-HTML pages) and whether the call is billed on failure.

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

Conciseness3/5

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

It is short and front-loaded with the primary purpose, but the returned fields are enumerated twice — first as 'title, meta description, canonical URL, Open Graph and Twitter card tags' and again in the 'return ...' sentence — which is redundant. The pricing and demo sentences are justified and earn their place.

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 carries the burden of describing return contents and does so thoroughly, plus it discloses cost and access constraints. The remaining gap is that it does not say what the response looks like when a page has no metadata or is blocked by robots.txt.

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?

Schema coverage is 100% and there is a single 'url' parameter already documented as a public http(s) URI with a 2048-char cap. The description reinforces the 'public page' constraint but adds no format, normalization, or redirect-handling detail beyond the schema, so the baseline 3 applies.

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 uses a specific verb ('Get') and enumerates the exact resource fields returned: title, meta description, canonical URL, Open Graph and Twitter card tags, H1, icons, manifest, alternates, JSON-LD count. It is clearly distinguishable from a plain text-extraction tool, but it never names a sibling (e.g. web_markdown or web_sitemap) to sharpen the boundary.

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 phrase 'Ideal for link previews and SEO checks' gives implied use cases, and 'Fetch a public page (respects robots.txt)' implies the eligibility constraint. However, there is no explicit when-not guidance and no routing to alternative sibling tools for adjacent tasks, leaving the agent to infer boundaries.

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