Skip to main content
Glama

Get a page's metadata

meta
Read-only

Get a page's metadata: title, description, canonical URL, language, Open Graph and Twitter card (including preview image), icons, RSS feeds, JSON-LD types, H1s, link and word counts. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, yet the description adds genuinely new behavioral facts: a latency claim (under 2 s), a metered quota (20 free calls/day per user across free tools), and a pay-per-call model via x402 USDC on Base. It still does not cover failure modes such as unreachable URLs or cache behavior, but the cost/auth disclosure is well beyond annotation scope.

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?

Front-loaded with the output inventory, then a compact pricing sentence; every sentence carries information. The pricing clause consumes roughly a third of the text but is decision-relevant for an agent that must budget calls, so it earns its 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?

No output schema exists, so the description must enumerate return values, and it does so thoroughly across title, canonical URL, social cards, icons, feeds, JSON-LD, and counts. Combined with the disclosed cost/payment flow, an agent has enough to call it correctly; only error/edge-case behavior is unaddressed.

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 both parameters (url, payment) are documented in the schema, including the 'omit on first call to get price and requirements' flow, so baseline 3 applies. The description corroborates the payment model but adds no syntax or format detail beyond what the schema states.

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?

States a specific verb ('Get') plus resource ('a page's metadata') and enumerates the returned fields (title, canonical URL, Open Graph/Twitter cards, JSON-LD types, H1s, link/word counts), which lets an agent know the payload shape without opening a schema. It does not distinguish itself from overlapping siblings such as headings, links, or feeds, which also surface some of the same data.

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 context is implied rather than stated: the free-tier limit and $0.002-per-call pricing tell the agent to be economical, but there is no explicit when-to-use / when-not-to-use guidance relative to sibling tools like seo_audit, headings, or links. The agent must infer that this is a broad first-pass metadata fetch.

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.