Skip to main content
Glama

Sitesy Website Intelligence

Page metadata

page_metadata
Read-onlyIdempotent

Title, description, canonical, Open Graph and Twitter card tags, icons, and structured data types from one web page. Costs 0.002 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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
urlYesA web page address, for example https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety baseline is covered. The description then adds behavior the annotations cannot express: a per-call price of 0.002 USDC on Base paid via x402, and the two-step first-call-returns-payment-requirements then sign-and-retry flow. That is exactly the kind of non-obvious runtime trait an agent needs before invoking the tool.

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?

Two sentences, front-loaded with the payload contents and followed by the payment mechanics; nothing is wasted. There is slight redundancy between 'Costs 0.002 USDC per call' and the following sentence restating per-call USDC payment.

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?

For a one-parameter read tool with no output schema, the description is complete: it enumerates the returned metadata categories and explains the non-obvious payment handshake that would otherwise cause a confusing first-call failure. Remaining unknowns such as rate limits or JS rendering are marginal for this tool class.

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?

There is a single parameter with 100% schema description coverage (format uri, maxLength 2048, example supplied), so the schema carries the load and the baseline is 3. The description adds no constraint on the URL, such as whether redirects are followed or how non-HTML targets are handled.

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 names the exact extraction: title, description, canonical, Open Graph/Twitter tags, icons, and structured data types from a single web page. That is a specific verb+resource and clearly narrower than a full-content sibling like page_reader, though no sibling is named outright.

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 only implied by scope: an agent can infer 'one page, metadata only' versus fetching page content or links. There is no explicit when-to-use or when-to-prefer-an-alternative statement, so the agent must reason about routing itself.

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