Skip to main content
Glama

Page meta

page_meta
Read-onlyIdempotent

Extract SEO metadata from a web page: title, meta description, canonical, Open Graph, Twitter cards, h1s, and JSON-LD types. $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": "page_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL
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.2/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description's job is to add what they cannot: it discloses the price ($0.001 per call), the x402 payment protocol, accepted currencies and chains (USDC on Arc/Base/Solana, XNT on X1), and the two-call handshake required to complete a purchase. An agent knows the cost and the failure mode (no payment = terms only) before invoking.

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?

Three sentences, front-loaded with what is extracted, followed by cost and the payment handshake. Every clause earns its place; the middle sentence is dense with chain/token detail but is operationally necessary rather than filler. Slightly heavy nesting of payment specifics keeps it from a 5.

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, so the field enumeration carries the return-value burden, and it does that well. The two-step payment flow is fully explained. Minor gaps remain: no mention of behavior on non-HTML pages, redirects, or error responses when payment terms are rejected.

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 both parameters are already documented, and the baseline would be 3. The description adds genuine meaning beyond the schema by explaining that the first call returns terms and the second call with the signed `payment` payload completes the purchase inside the same tool call — context the schema's "base64 payload" note does not convey.

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 and resource ("Extract SEO metadata from a web page") and enumerates the exact fields returned — title, meta description, canonical, Open Graph, Twitter cards, h1s, JSON-LD types — which implicitly separates it from full-text siblings like page_extract or page_markdown. It never explicitly names a sibling or states the boundary, so it falls short of the top tier on differentiation.

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?

It gives a concrete procedural rule for the payment flow: call once without `payment` to obtain terms, sign with your own wallet, call again with `payment`. That is clear usage context for the paid path. It does not say when to choose this tool over page_extract/site_extract, nor any prerequisites about the target site (robots, auth-gated pages).

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